Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!hellgate.utah.edu!helios.ee.lbl.gov!nosc!manta!psm
From: psm@manta.NOSC.MIL (Scot Mcintosh)
Newsgroups: comp.realtime
Subject: vxWorks tcp question
Message-ID: <1032@manta.NOSC.MIL>
Date: 15 Mar 90 16:12:08 GMT
Reply-To: psm@manta.nosc.mil.UUCP (Scot Mcintosh)
Distribution: usa
Organization: Naval Ocean Systems Center, San Diego
Lines: 15

We're using vxWorks, but unfortunately didn't purchase the
source code.  It looks like vxWorks is using silly-window
avoidance on its tcp connections and that causes us some
problems.  We need to be able to force out whatever data 
is awaiting transmission on a particular socket, and Wind
River's suggestion of setting the NODELAY socket option
isn't doing any good. Because things are dynamically linked
under vxWorks, we can make calls to the internal tcp routines.
Can anyone suggest how to accomplish a forced transmission?

-- 
----
Scot McIntosh
Internet: psm@helios.nosc.mil
UUCP:     {ihnp4,akgua,decvax,decwest,ucbvax}!sdscvax!nosc!psm