Currently, profile result negotiation is attached to a
Service Group,
which is, essentially, a service. The following is not
clear to me:
- can two profiles be negotiated for the same group?
Currently not.
We do not explicitly allow or prohibit this, right? Should I
explicitly prohibit in the Core?
Maybe we should add to OCP core that only the last negotiated profile
for a service group is valid.
Do you really think we need of a copy constructor of service groups?
I think that since service groups only need to be created at the
beginning of connections and these connections can then create any
number of transactions, optimization in this area is not critical.
Let's not optimize, then. The feature can be added later, if needed.
Agreed.
Martin