[omniORB] Connected client IP address
Ridgway, Richard (London)
Richard_Ridgway at ml.com
Fri Jun 5 12:02:39 BST 2009
Yet we have to recognise that where something is so commonly wanted that
it gets implemented in an ad-hoc manner in all the different
implementations of the standard, perhaps the standard itself is lacking.
Certainly all the orbs I have worked with provide this facility somehow,
and I have wanted to make use of it on a few occasions.
In this case we know we can guess why the standard is lacking: knowledge
of an ip address implies the existence of an ip address which implies
the transport being used, and corba doesn't.
-----Original Message-----
From: omniorb-list-bounces at omniorb-support.com
[mailto:omniorb-list-bounces at omniorb-support.com] On Behalf Of Nigel
Rantor
Sent: 05 June 2009 10:42
To: Marco Ferreira
Cc: omniorb-list at omniorb-support.com
Subject: Re: [omniORB] Connected client IP address
Marco Ferreira wrote:
> Hello all.
>
> Is there any way to grab the client IP that made the call to a method,
> in python?
Not through an official CORBA interface there isn't, that's one of the
levels of transparency CORBA attempts to provide.
Other than that, I don't know, I'm sure Duncan can point out a
reach-around...
<soapbox>
You really probably shouldn't do that anyway, you're just going to end
up losing some of the goodness that CORBA was meant to provide you with.
If you want to tell us what your real problem/use-case is then I'm sure
we'd be more than happy to consider a solution that might work and not
involve deep knowledge (well, deeper than CORBA provides) into the
underlying system you're running on.
</soapbox>
n
_______________________________________________
omniORB-list mailing list
omniORB-list at omniorb-support.com
http://www.omniorb-support.com/mailman/listinfo/omniorb-list
--------------------------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------------------------
More information about the omniORB-list
mailing list