In an effort to learn Twisted, I am working on a set of small client and
server applications which utilize PB as IPC. The server hosts a group of
simple parameters that clients may monitor or set. For a client to
monitor a parameter's value, it seems that the server should create the
parameter
Thank you very much for your responses, the problem seems to appear when in
my tests I send the file "to myself", when I send files over the network,
the things goes well. I suspect (it's just a suspect) that the code spawns
too much deferreds too much fast, causing the loop not to complete (or
so
After putting some strategical sleeps seems that the problem is that the
application is the server and the client at once, I think that this
generates a "loop" in the mainloop.
2010/5/23 Gabriele Lanaro
> Thank you very much for your responses, the problem seems to appear when in
> my tests I se
Finally I managed to solve myself this obscure bug. I put the
reactor.iterate() call before spawning new callbacks, in this way I force
the mainloop to complete the cycle. The pseudocode would be modified in this
way:
Client()
proceed_sending():
chunk_tot = CHUNK_TOT
chunk
Hey everyone, I've still been trying to track down this spin bug. What
I probably should have mentioned before is that these are SSL
connections. Looking through the 10.0 release code, I found the
_sendCloseAlert method in tcp.py: http://pastebin.com/gZKxHtN5
I feel like this is almost certainl
I use PB in unstable network. The server remembers the last answer.
Client detection disconnected, connected again, makes entry into the
system and calls the function returns the last response
(get_last_response). The answer, it returns a deferred saved earlier.
If somewhere an error cycle repeats.
On 12:21 pm, gabriele.lan...@gmail.com wrote:
>Finally I managed to solve myself this obscure bug. I put the
>reactor.iterate() call before spawning new callbacks, in this way I
>force
>the mainloop to complete the cycle. The pseudocode would be modified in
>this
>way:
>
>Client()
>proceed_se
In which sense it's invalid? I don't know how the gtk reactor works, I just
guessed that the event loop never reaches the gui events. My idea was to
force the processing of these events before spawning another deferred, it's
just a workaround, the real problem is the fact that the server and the
c
On May 23, 2010, at 6:36 PM, Gabriele Lanaro wrote:
> In which sense it's invalid? I don't know how the gtk reactor works, I just
> guessed that the event loop never reaches the gui events. My idea was to
> force the processing of these events before spawning another deferred, it's
> just a wo
On May 23, 2010, at 11:54 AM, Viktor Klimov wrote:
> I use PB in unstable network. The server remembers the last answer.
> Client detection disconnected, connected again, makes entry into the
> system and calls the function returns the last response
> (get_last_response). The answer, it returns a
On 23 May, 12:26 am, gl...@twistedmatrix.com wrote:
>The nice thing about Twisted's compatibility policy is that developers,
>and even users, very rarely have problems when installing a new version
>of Twisted. While this is a nice benefit, the current strategy of
>developing features in a comp
11 matches
Mail list logo
