> > On 25.02.06 21:02, Andrew M. Bishop wrote: > > > I don't know how this particular web page works, but it is not > > > possible for a server to push data out to the browser, only the > > > browser can request it from the server. If you have set the options > > > so that WWWOFFLE is not caching the page then it should work as well > > > with WWWOFFLE as without it.
> Matus UHLAR - fantomas <[EMAIL PROTECTED]> writes: > > They are the data from one POST request. Seems that wwwoffle buffers them > > somehow and doesn't send them imediately to the client. On 12.04.06 19:27, Andrew M. Bishop wrote: > WWWOFFLE will read all of the POST request from the client (browser) > and then send all of it to the server. The data comes back from the > server and is sent straight to the client. WWWOFFLE does not hold on > to the data for longer than it needs to. This is what seems not to be completely true. I've noticed the same behaviour yesterday, with different application (albums at http://digi.perseus.sk/) - without wwwoffle pictures load smoother. There may be some buffering at input or ourput at wwwoffle or socket level, which causes delays. Could you please check it? > > Apr 11 14:42:03 fnote wwwoffles[5965]: Client is 'HTTP/1.1' we choose to > > use chunked encoding. > > Apr 11 14:42:03 fnote wwwoffles[5965]: > > URL='http://chat.irc.sk/cgi-bin/client-perl.cgi?R=rz7l2gus52x3&cmd=quit'. > > Apr 11 14:42:03 fnote wwwoffles[5965]: proto='http'; host='chat.irc.sk'; > > path='/cgi-bin/client-perl.cgi'; args='R=rz7l2gus52x3&cmd=quit'; > > user:pass='(null):(null)'. > > Apr 11 14:42:03 fnote wwwoffled[1251]: Forked wwwoffles -real (pid=5965). > > Apr 11 14:42:03 fnote wwwoffles[5965]: Server has used 'Transfer-Encoding: > > chunked'. > > Apr 11 14:42:03 fnote wwwoffles[5965]: Cache Access Status='Not Cached'. > > Apr 11 14:42:03 fnote wwwoffles[5965]: Using 'Transfer-Encoding: chunked' > > for the client. > > Apr 11 14:42:03 fnote wwwoffles[5965]: Server bytes; 325 Read, 613 Written. > > Apr 11 14:42:03 fnote wwwoffles[5965]: Client bytes; 564 Read, 349 Written. > > The request came in to WWWOFFLE, was not cached and sent to the server > and all finished within one second. > > > The request lasted for a few minutes - until I clicked at "exit" button in > > the generated page. > > I don't understand what you mean by this. Did you see any other > WWWOFFLE requests during this time? Did you expect any other requests > during this time? no other requests, only one at all. IT seems to me that the gateway works as one long-standing POST request which receives data and sends them in parallel. -- Matus UHLAR - fantomas, [EMAIL PROTECTED] ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. There's a long-standing bug relating to the x86 architecture that allows you to install Windows. -- Matthew D. Fuller
