[omniORB] Latencies - Oneway vs. Roundtrip

Helge Penne Helge.Penne@datarespons.no
Fri, 16 Apr 1999 08:42:46 +0200


Jim Redman wrote:

> Thanks to the group and Helge for the proposed solution.
>
> At 06:44 PM 4/13/99 +0100, Sai-Lai Lo wrote:
> >I think it has been pointed out already that we do not set TCP_NODELAY by
> >default. You probably want to play with setsockopt to see if the behaviour
> >changes.
> >
> >From my admittedly narrow point of view I can't think of a use for oneway
> where latency is not important.  If I was simply trying to move a large
> amount of data and didn't care about latency I probably wouldn't send out a
> bunch of small messages.  I use oneway because I need each tiny piece of
> data to arrive as soon as possible after it is generated.  If this is the
> normal reason then I could make a case for TCP_NODELAY being the default.
>
> Jim

I'll second that.  I think the omniORB deserves a startup option that will let
you turn this behaviour on or off.

As to the proposed solution: Not that it was NT specific, and may not work on
other platforms.  As Mr. Jørgensen pointed out, level=SOL_SOCKET should
probably be used on other platforms.  Om my NT 4.0 computer, SOL_SOCKET does
not work (gives no error, but no chance in behavior either).  This would
indicate that a portable solution would have to use some #ifdef <platform>
switches to make it work across different platforms.  I guess Microsoft's API
could be to blame.

- Helge