Hi Jason,
your project sounds interesting!
I would suggest you put the code into http://gitorious.org/.
Then people can fork and build on it.
If i understand it correctly the application would run as
a webserver application and all events are sent over a socket between
the browser and the webser
terça-feira, 10 de setembro de 2013 17:29:19, Benjamin Zeller wrote:
I did some more debugging today, something changed but its still
crashing at the same place:
- The QAbstractSocket now has a QAdoptedThread affinity
- The QAbstractSocket has a 0x0 pointer to the engine
- The QAbstractSocketEngine
ck to
the mainthread? Would the move be correct?
I think QSocketNotifier uses a posted event to reenable itself after
a move... which means this is not delivered properly
On 09.09.2013 23:07, Thiago Macieira wrote:
> On segunda-feira, 9 de setembro de 2013 21:46:56, Benjamin Zeller wrote:
>&g
On 09.09.2013 19:30, Thiago Macieira wrote:
> On segunda-feira, 9 de setembro de 2013 18:10:25, Benjamin Zeller wrote:
>>> 2) there's a lingering bug in the dispatcher that causes it to send events
>>> to objects that have recently been moved away. For example, it
On 09.09.2013 17:37, Thiago Macieira wrote:
> On segunda-feira, 9 de setembro de 2013 15:18:26, Benjamin Zeller wrote:
>> sendEvent is used, but the receiver is in another thread, shouldn't it
>> use postEvent or better shouldn't the threads eventloop do this stuff?
Hello,
i'm currently stress-testing a application at work and came across this
problem.
The application accepts connections and pushes the created sockets
to a worker thread (moveToThread), the worker thread then handles the
rest.
But sometimes when the socket was already closed in the thread i
ge
05.09.2013 14:27, Benjamin Zeller wrote:
> On 05.09.2013 14:09, Etienne Sandré-Chardonnal wrote:
>> Hi,
>>
>> Did you see this in the doc?:
>> *Note:*The returnedQTcpSocketobject cannot be used from another thread.
>> If you want to use an incoming con
or would be better but the design of
the library does not really fit that approach.
>
> (From Qt 4.8.1)
>
>
> 2013/9/5 Benjamin Zeller <mailto:zeller.benja...@web.de>>
>
> Hello again,
>
> ok after digging some more its clear that the E_AGAIN or E_WOUL
delay the notification of new incoming connecions
until another one is handled?
On 05.09.2013 13:04, Benjamin Zeller wrote:
> Hello,
>
> not sure if i just ran into a bug or if i do something wrong:
>
> Basically i have a QTcpServer accepting connections, after a connection
> com
Hello,
not sure if i just ran into a bug or if i do something wrong:
Basically i have a QTcpServer accepting connections, after a connection
comes in a QTcpSocket is created and pushed to a workerthread to handle
it (moveToThread).
But after 6 connections the QTcpServer stops accepting connectio
10 matches
Mail list logo
