W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1996

Is STDOUT flushed?

From: bpm <bpm@terraweb.com>
Date: Thu, 21 Nov 1996 16:26:06 -0600
To: www-jigsaw@w3.org
Message-ID: <19961121222606.AAA7173@vlad.terraweb.com>

I am in the process of setting up Fast CGI applications to run under
Jigsaw.  (This is an interim step until I can get the apps
re-written!)  I am using the fast-cgi development kit from the
www.fastcgi.com (Open Market) site.  They have a cgi-fcgi application
that is a cgi to fcgi gateway.  You can set up a CgiResource that calls
a script that invokes the cgi-fcgi gateway and run the fastCGI
application.  It works really great, except for one item that has me
baffled.  On the initial connection to the fastCGI application, the
browser waits and spins.  The browser is waiting for an EOF from the
server.  If I click on the "Stop" menu button, I get a:

Transfer interrupted!
on the browser screen.  But I can go ahead and fill out the form,
submit and it works fine.  ANY OTHER connections to the fastCGI
application works just fine.  It is just the initial connection.

NCSA 1.5 used to have this same condition until Brandon Long noticed
that he was closing the file handle without flushing.

I looked at the w3c.jigsaw.http.Client.java emitReply method, but it
looks like output is being flushed.

Any ideas?


Brian Millett                    
Technology Applications Inc.     "Heaven can not exist,
(314) 530-1981                          If the family is not eternal"
bpm@techapp.com                   F. Ballard Washburn
Received on Thursday, 21 November 1996 17:23:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:30 UTC