On Mon, 31 May 2010, Qoo Goo wrote:
> Haha, interesting discussion. Yes. If you do not flushes data before..
> I've seen these past days people out there saying (it's easy to find
> it googling) that the correct way to do things is:
>
> Response.Flush()
> Response.Close()
> Response.End()
A 100'000 flies can't be wrong ...
>> Here is the relevant section from RFC793 (TCP) pertaining to what happens on
>> the server and client sides of a close:
>
> Yes, but is generally the OS who should handle all this stuff.
And the OS did, what it was asked for, it dropped the connection.
That's why you do
sync;sync;reboot
and not just
sync;reboot
I believe ...
> The browser should only deal with higher layers. Just "give me data, pls".
> And it happens only with specific versions...
So you are relying on some versions of the browser guessing what you meant
...
> Yes, I know: I am trying to make our bug smaller by trying to
> demonstrate it was caused in part by a hyper-giant Google's bug :-)
... while you did something wrong.
Cheers,
Fritz
--
Oetiker+Partner AG tel: +41 62 775 9903 (direct)
Fritz Zaucker +41 62 775 9900 (switch board)
Aarweg 15 +41 79 675 0630 (mobile)
CH-4600 Olten fax: +41 62 775 9905
Schweiz web: www.oetiker.ch
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
