On 6/18/07, 甜瓜 <littlesweetmelon at gmail.com> wrote:
> Thank you for your kind reply.
>> > Something like ClientCreator (a convenient way to connect and get a protocol
> > instance when it is connected) with blockingCallFromThread (in SVN Twisted, so
> > the calling thread can get access to the result of the deferred from
> > ClientCreator) would probably do the trick.
> >
>> ClientCreator is not proper for my case, because I need the re-connect ability.
>> Well, actually, my project is based on this article:
>http://solipsis.netofpeers.com/wiki2/index.php/WxPython_And_Twisted_Example> a VERY GOOD implementation for cooperation between wx and twisted.
> The hard nut is how to make DaemonLoop know the protocol instance
> which is connecting to the remote server. ^_^
>> ---
This is a terrible implementation for cooperation between wx and
twisted. At the time it was written, it was acceptable, but you really
should be using the wxreactor now.