he client's fault? So I could also still be TOTALLY wrong.
> Sent: Thursday, April 04, 2019 at 10:41 AM
> From: "alexander golks" <a...@golks.de>
> To: No recipient address
> Cc: interest@qt-project.org
> Subject: Re: [Interest] QWebSocketServer - server rand
.
>
> > Sent: Thursday, April 04, 2019 at 10:41 AM
> > From: "alexander golks"
> > To: No recipient address
> > Cc: interest@qt-project.org
> > Subject: Re: [Interest] QWebSocketServer - server randomly stops
> accepting connections
> >
> >
uot;), so maybe it's the client's fault?
So I could also still be TOTALLY wrong.
> Sent: Thursday, April 04, 2019 at 10:41 AM
> From: "alexander golks"
> To: No recipient address
> Cc: interest@qt-project.org
> Subject: Re: [Interest] QWebSocketServer - server randomly s
e handhake bytes may come in slowly and take multiple re-parsings,
> (something to add to your fuzzer?) but you can wind up in an uncaught error
> state.
>
>
>
> Sent: Thursday, April 04, 2019 at 10:07 AM
> From: "Jason H"
> To: "Narolewski Jakub"
terest@qt-project.org
Subject: Re: [Interest] QWebSocketServer - server randomly stops accepting connections
So, yeah, I was thinking of QTcpServer::incommingConnection(). That function is used in multithreadding because you use the descriptor to make a socket on the proper thread. Looks like QWeb
stops working for whatever reason?
Sent: Thursday, April 04, 2019 at 9:13 AM
From: "Narolewski Jakub"
To: "Jason H"
Cc: interest@qt-project.org
Subject: Re: [Interest] QWebSocketServer - server randomly stops accepting connections
That's the thing. I alread
That's the thing. I already handle connections and disconnections in my
code - including logging relevant information.
When I implemented this I heavily based on the example that you linked to.
WSS communication is single threaded - only way to communicate with the
outside world from different
: "Jakub Narolewski"
To: "interest@qt-project.org"
Subject: [Interest] QWebSocketServer - server randomly stops accepting connections
I have this one, strange problem with QWebSocketServer that is driving me insane.
My project is a very simple, websocket-based online game se
I have this one, strange problem with QWebSocketServer that is driving me
insane.
My project is a very simple, websocket-based online game server. It uses Qt SQL
modules and makes use of some light QEvent'ing.
Up until recently I used uWebSockets to drive my wss communications. To make
matters
