Hi,
Actually it macextras is intentionally left out from iOS packages, see
discussion in https://bugreports.qt-project.org/browse/QTBUG-41476
br,
Jani
Lähettäjä: Thiago Macieira
mailto:thiago.macie...@intel.com>>
Päiväys: 20. joulukuuta 2014 2.53.51 UTC+2
Vastaanottaja: mailto:interest@qt-proj
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 mig
On Sunday 21 December 2014 22:57:06 Guido Seifert wrote:
> Thiago, do you know by any chance how costly it is to open and close a
> socket? When this always happens when data is sent over my QWebSocket and
> I have several clients... this cost might add up.
That depends on the OS. On Linux, it's
> > If you're implementing an HTTP server, close TCP connections that didn't
> > send
> > any requests within a reasonable amount of time.
>
> Sure, that's what I do now.
And this is what I just stopped doing. Stupid me... always trying the hard way
first,
instead of the correct way... When
> Why is it a memory leak?
When I get a socket from QTcpServer... who is responsible for its deletion?
Since I never expected to get such dead connections, I did not handle them
correctly. I deleted them after I got data.
> If you're implementing an HTTP server, close TCP connections that didn'
On Sunday 21 December 2014 20:30:40 Guido Seifert wrote:
> However, each time my QTcpServer also fires and gives me another QTcpSocket.
> Nothing ever comes through this new QTcpSocket... but it is there and a
> memory leak.
Why is it a memory leak?
If you're implementing an HTTP server, close TC
On 21 December 2014 at 19:30, Guido Seifert wrote:
> However, each time my QTcpServer also fires and gives me another
> QTcpSocket.
> Nothing ever comes through this new QTcpSocket... but it is there and a
> memory leak.
>
Browsers can (and do) pre-emptively connect to servers if they think they
Friend helped me so I can now say this problem also does not
happen with Safari on iPhone.
Question is how to workaround this problem?
G.
Guido Seifert wrote:
> Hiya,
> I have here a very strange phenomena.
> I have a QTcpServer, which listens to my address at port 20203.
> When I connect
Hiya,
I have here a very strange phenomena.
I have a QTcpServer, which listens to my address at port 20203.
When I connect with Firefox to this port, a newConnection signal
is emitted. So far so good. I send my Firefox a html page. Means
I wrote a simple Http-Server. As soon as I sent this page,
