[omniORB] Issue with firewalls
Adnan Khan
akhan at proteligent.net
Mon Feb 9 09:53:05 GMT 2004
Hi Marco
I am already doing this; here are the client side options:
const char* options[][2] = { { "offerBiDirectionalGIOP", "1" },
{ "clientTransportRule", "* bidir,ssl,unix,tcp" },
{ 0, 0 }
};
CORBA::ORB_var orb = CORBA::ORB_init(argc, argv, "omniORB4", options);
Any further thoughts?
Thanks
Adnan
-----Original Message-----
From: Barthel Marco (MPA/DS) [mailto:Marco.Barthel at tenovis.com]
Sent: Monday, February 09, 2004 3:28 AM
To: Adnan Khan; omniorb-list at omniorb-support.com
Cc: adaimee at proteligent.net
Subject: AW: [omniORB] Issue with firewalls
> I was going through omniORB 4.0.3 documentation and found how
> to achieve
> Bi-directional GIOP, which allows callbacks to be made using
> a connection
> opened by the original client. Based on what's given in the
> documentation, I
> have added following code to the server as follows:
>
>
> const char* options[][2] = { { "acceptBiDirectionalGIOP", "1" },
> {
> "serverTransportRule", "* bidir, tcp" },
> { 0, 0 }
> };
did you specify a client-transport rule ??? On Callback der Server acts as
client.
I think you should use "clientTransportRule", "* bidir, tcp" on the
"Serverside" also.
Hope that helps.
-marco
More information about the omniORB-list
mailing list