[omniORB] Caller/request info in method execution

Ivanov, Roumen Roumen.Ivanov@dresdner-bank.com
Mon, 15 May 2000 17:13:52 +0200


Thanks to both of you. Let's say IP address/process ID or whatever that
would help to identify the client.
Roumen

-----Original Message-----
From:	Carlson, Andy [SMTP:andycarlson@att.com]
Sent:	Monday, May 15, 2000 17:08
To:	Duncan Grisby; Ivanov, Roumen
Cc:	'omniorb-list@uk.research.att.com'
Subject:	RE: [omniORB] Caller/request info in method execution 

... or use an implementation of the CORBA security service ...

... if you can find one that suits you ...

... but that will probably mean switching ORBs, these things are usually
tightly coupled to the ORB.

Andy
----------------------------------------------------------------------------
-----------
Andy Carlson. AT&T Labs (UK)   	Tel: +44 1527 495258
E-Mail: andycarlson@ipo.att.com	Fax: +44 1527 495229



> -----Original Message-----
> From:	Duncan Grisby [SMTP:dgrisby@uk.research.att.com]
> Sent:	Monday, May 15, 2000 3:56 PM
> To:	Ivanov, Roumen
> Cc:	'omniorb-list@uk.research.att.com'
> Subject:	Re: [omniORB] Caller/request info in method execution 
> 
> On Monday 15 May, "Ivanov, Roumen" wrote:
> 
> > 	Does anyone could help me to find some CORBA-compliant or
> > Omni-specific way to gather caller's/request's information during a
> method
> > execution?
> 
> What particular information do you require?  Neither the CORBA
> standard or omniORB let you find out anything about the client. It's
> best to explicitly send the information you need in arguments to the
> operation.
> 
> Cheers,
> 
> Duncan.
> 
> -- 
>  -- Duncan Grisby  \  Research Engineer  --
>   -- AT&T Laboratories Cambridge          --
>    -- http://www.uk.research.att.com/~dpg1 --