CORBA24 — Optimization of LOCATION_FORWARD replies

Summary: As of GIOP/IIOP 1.1, if a server wants to have a client
use some locally hashed down object_key in future requests
for an object, it must require one of the following:
a) the client use a LocateRequest in order for the server
to reply with a forwarded object reference that has
a hashed down object key.
b) respond with an OBJECT_FORWARD reply to the request,
forcing the client to remarshal the request with the
new target (the forwarded object reference"s key).
With some already recommended changes to GIOP 1.1,
such a reply will only require remarshaling the
message header, but an extra roundtrip is still required.

This could be avoided by addind a new service context
to the reply that contains the forward IOR, or a new
Reply type such as NO_EXCEPTION_AND_FORWARD that
indicates the first request has succeeded and that
subsequent requests can use the supplied forward IOR.

Close this previously deferred issue as too much for RTF. Add to GIOP future version "wish list" do