CORBA21 — Issue: Problem with issue 2801 resolution

Summary: > > Add the following paragraph to 15.8:
> >
> > "To avoid collisions of requestId in fragment messages when
> > bi-directional GIOP is in use:
> >
> > - a request may not be sent by an endpoint if a reply has been
> > sent by that endpoint without a terminating fragment.
> >
> > - a reply may not be sent by an endpoint if a request has been
> > sent by that endpoint without a terminating fragment."
> >
>
> Why is a plain (non-fragmented) request/reply prohibited here? There has
> never been and feature interaction between fragmented request/replies and
> non-fragmented ones, so why have this restriction.

Jishnu Mukerji wrote:

> After poking around some it seems to me that the following words address
> Martin"s concern and hence the issue of inadvertently disallowing something
> that wasn"t broken in the current resolution of 2801. The additional word
> "fragmented" in two places is bracekted between "*"s.
>
> "To avoid collisions of requestId in fragment messages when
> bi-directional GIOP is in use:
>
> - a fragmented request may not be sent by an endpoint if a
> fragemented reply has been sent by that endpoint without a terminating
>fragment.
>
> - a fragemented reply may not be sent by an endpoint if a
> fragmented request has been sent by that endpoint without a terminating
>fragment."

resolved, see below