<font size=2 face="sans-serif">Hi Duncan </font>
<br><font size=2 face="sans-serif">How to do and if so is there any example
?</font>
<br>
<br><font size=2 face="sans-serif">Thanks and regards<br>
<br>
Ravi Kumar Kulkarni<br>
POWER Firmware Development India<br>
MK GF 129 Manyatha K Blk<br>
ISTL, Bangalore<br>
Extn: 56822<br>
Mobile : 9731371000<br>
rkulkarn@in.ibm.com</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">Duncan Grisby <duncan@grisby.org></font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">Ravi K Kulkarni/India/IBM@IBMIN</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Cc:
</font><font size=1 face="sans-serif">omniorb-list@omniorb-support.com</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">12/12/2014 05:35 PM</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">Re: [omniORB]
Using TCP_USER_TIMEOUT in OmniORB4.1.6 ?</font>
<br>
<hr noshade>
<br>
<br><tt><font size=3>On Fri, 2014-12-12 at 14:12 +0530, Ravi K Kulkarni
wrote:<br>
</font></tt>
<br><tt><font size=3>[...]<br>
> So one of the option was to use TCP_USER_TIMEOUT<br>
> ( </font></tt><a href="http://man7.org/linux/man-pages/man7/tcp.7.html"><tt><font size=3>http://man7.org/linux/man-pages/man7/tcp.7.html</font></tt></a><tt><font size=3>)
so we can have a<br>
> control over TCP to TCP communication.<br>
><br>
> Questions :<br>
><br>
> 1/. Is there a way to get the Socket Descriptors value from a Object<br>
> Reference ?. If so, I can get the sockfd and then do a setsockopt<br>
</font></tt>
<br><tt><font size=3>Object references do not have their own sockets --
omniORB opens<br>
connections on demand, and reuses connections for multiple objects in<br>
the same address space. Any particular object reference can have any<br>
number of sockets associated with it.<br>
</font></tt>
<br><tt><font size=3>> 2/. Will OmniORB provide any mechanism to make
use of<br>
> TCP_USER_TIMEOUT ?<br>
</font></tt>
<br><tt><font size=3>It's not really something you are expected to do,
so it is not easy to<br>
get hold of the sockets inside omniORB's connections, but it is possible<br>
if you access lots of omniORB internal data structures. You can define
a<br>
clientOpenConnection interceptor and then reach through the objects to<br>
finally get to the socket. It's not pretty, though, and the headers for<br>
some of the required class definitions are not even installed in a<br>
normal omniORB install.<br>
</font></tt>
<br><tt><font size=3>The easiest way for you to achieve it is probably
to patch omniORB to<br>
set the socket option as it opens the connections. Search for uses of<br>
setsockopt in the code, and you'll see where you can set your additional<br>
option.<br>
</font></tt>
<br><tt><font size=3>Duncan.<br>
</font></tt>
<br><tt><font size=3>--<br>
-- Duncan Grisby --</font></tt>
<br><tt><font size=3>-- duncan@grisby.org --<br>
-- </font></tt><a href=http://www.grisby.org/><tt><font size=3>http://www.grisby.org</font></tt></a><tt><font size=3>
--</font></tt>
<br>
<br>
<br>
<br>