This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author adamhj
Recipients adamhj, giampaolo.rodola
Date 2012-02-04.13:31:32
SpamBayes Score 0.00016108071
Marked as misclassified No
Message-id <1328362293.2.0.214016127596.issue13928@psf.upfronthosting.co.za>
In-reply-to
Content
ah just ignore my previous msg as i post it without seeing yours.

> Nope. It means that *before* showing up the socket was *not* connected.
ok, i read more in the asyncore source and finally understand what do you mean by "A non connected socket must be writable in order to connect". i think this is a little confusing if without any explaining, shouldn't this be written into the asyncore reference page as both readable() and writable() may be override by user?

> Of course it does: you're not connected yet (10057 = WSAENOTCONN). 
> You're supposed to use send() in handle_connect(), when the connection has already been established.
> This:
>
>     self.connect()
>     self.send('hello')
>
> ...is not asyncore is supposed to be used.

oh it seems i forgot handle_connect(), thank you for your patient explanation and sorry to have troubled you. i think there is no problem anymore
History
Date User Action Args
2012-02-04 13:31:33adamhjsetrecipients: + adamhj, giampaolo.rodola
2012-02-04 13:31:33adamhjsetmessageid: <1328362293.2.0.214016127596.issue13928@psf.upfronthosting.co.za>
2012-02-04 13:31:32adamhjlinkissue13928 messages
2012-02-04 13:31:32adamhjcreate