[omniORB] Interceptor interfaces

[William Noon]

Duncan -- I am using it to provide a security token that identifies
the client.  Most of my code is in python so I have a module that
adds the interceptors for both 'clientSendRequest' to send the 
token (if set) in a service context and 'serverReceiveRequest' 
to pull it out of the service context and record the remote ip
address.

The module also adds methods to get/set the token.

What type of changes are you contemplating?  I am currently
adding the interceptors at module init, which is before ORB_init(),
with no problems.  Should I have some?

If you could add support for 'serverSendReply' and 'clientReceiveReply'
so I can set the token from the server code without client 
intervention, it would make the client code cleaner.

--Bill Noon
Northeast Regional Climate Center
Cornell University

> 
> Is anyone using omniORB 4's interceptors in real code?  How upset
> would you be if the interface was changed a bit?  I'm contemplating
> changing it to be a bit more general, and more efficient. One thing
> that might change is that you might have to register interceptors
> before ORB_init(), rather than after as it is now.
> 
> While I'm changing things, does anyone have any requests about
> interceptor features?  (If your request is for the portable
> interceptors API, then you're out of luck for now...)
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --
>