On Apr 20, 3:01 pm, Jean-Paul Calderone
wrote:
> You didn't let the program run long enough for the later events to
> happen. loop(count=1) basically means one I/O event will be processed
> - in the case of your example, that's an accept(). Then asyncore is
> done and it never gets to your custo
On Apr 20, 12:25 pm, Dun Peal wrote:
> Hi,
>
> I'm writing and testing an asyncore-based server. Unfortunately, it
> doesn't seem to work. The code below is based on the official docs and
> examples, and starts a listening and sending dispatcher, where the
> sending dispatcher connects and sends a
Hi,
I'm writing and testing an asyncore-based server. Unfortunately, it
doesn't seem to work. The code below is based on the official docs and
examples, and starts a listening and sending dispatcher, where the
sending dispatcher connects and sends a message to the listener - yet
Handler.handle_rea
-- Forwarded message --
From: Indy <[EMAIL PROTECTED]>
Date: Jan 25, 2007 11:27 PM
Subject: Re: asyncore.dispatcher.handle_read
To: Jordan <[EMAIL PROTECTED]>
OK, problem fixed. Thanks anyway :-)
On 25 Jan 2007 10:08:01 -0800, Jordan <[EMAIL PROTECTED]> wro
That was not entirely helpful, it's way more likely a mistake you made
in subclassing dispatcher than a problem within asycore itself (that
ended up sounding a lot more mean/angry than intended, sorry ¬_¬ ),
you really need to show us what changes you made to asyncore.dispatcher
if you want help.
Greetings.
I am writing an asynchronous server, and I use the standard library's
module asyncore.
I subclass asyncore.dispatcher. handle_accept works just right, that
is, when a client socket makes a request to connect to my server
socket, things that I set in handle_accept definition, happen. So,
