[Interest] Strange QWebSocket/QTcpServer interaction... Bug in Firefox?
pattyn.kurt at gmail.com
Mon Dec 22 11:18:08 CET 2014
Have you tried playing with the cache and expiry settings in the meta tags of the HTML page?
Maybe that can help?
> On 22 Dec 2014, at 07:30, Guido Seifert <wargand at gmx.de> wrote:
> Ok, thank you. So it really might be a problem for me. Fortunately the FF will be one
> of the least important browsers for my project. I decided, that this really is a FF
> bug, and regardless what the FF devs might say not a feature. I understand it, when a
> browser fetches pages, which I only might want to get. But I send mine a single html
> page with no further links, so it really downloads everything there is. Opening a socket
> to this page's address and port whenever the page sends data to a totally different
> websocket connection does not make not the least bit of sense.
>> That depends on the OS. On Linux, it's fairly inexpensive (besides the TCP/IP
>> cost of handshake), but on Windows it might be expensive.
>> And as evidence shows, browsers do open connections early so that the users
>> won't notice the latency. Then again, this is for Internet connections where
>> the handshake roundtrip can be hundreds of milliseconds.
> Interest mailing list
> Interest at qt-project.org
More information about the Interest