simple forking server -> problem (C) (fwd) (solved)

[Peter L. Peres]

On Fri, 3 Dec 2004, Lennart Sorensen wrote:

> On Wed, Dec 01, 2004 at 07:11:17PM +0200, Peter L. Peres wrote:
>>> If you are doing HTTP connections, you could just make your server
>>> return an http 1.0 header rather than 1.1, since 1.0 does NOT allow
>>> persistent connections.  That should prevent the browser from trying to
>>> use the same connection again and again.  You still have to force the
>>> browser to try multiple connections at once of course.
>>>
>>> There should also be a setting in the browser to control how many
>>> simultanious connections it will make.
>>
>> But ... I *want* persistent connections. I am experimenting with streams.
>
> Well a stream should just be one contiinous data flow through a
> connection.  It has nothing to do with persistant connections.
> persistant connections means multiple endependant http requests will be
> done through one socket connection (so without closing it at the end of
> the first request.
>
> If the browser won't do multiple streams at a time, perhaps it's
> connection limit is set too low.

In this case I use multiplexed streams, where the stream is a sequence of 
MIME encapsulated blocks that pass through the same connection, which is 
held open. So there should be exactly one open connection per client, 
followed by one request, followed by one response which consists of stream 
data, sent as MIME encapsulated blocks through that open connection. And 
that is so, but not with the browsers which optimise the connection. So 
'my' side of the problem is ok, it's the browsers that do not like this 
mode. Again, wget, netpipe etc all work ok with this mode.

Peter
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml