This reminded me of something I read years ago from Doug Schmidt on a pattern
half sync half async:
http://www.cs.wustl.edu/~schmidt/PDF/PLoP-95.pdf
I feel it is relevant but the picture may be upside down in relation to writing
twisted wrappers which may want to wrap a blocking API.
On Aug 2
This looks like the kind of thing that could involve using Deferred as part of
solution. Instead of callLater(0.8,doWrite), design the mechanism to wire up
event-source to fire the deferred and make doWrite be the callback.
On Oct 20, 2012, at 8:29:10AM, gelin yan wrote:
> Hi All
>
> A few
half async/half sync is not as obscure as you may think:
www.cs.wustl.edu/~schmidt/PDF/PLoP-95.pdf
On May 17, 2012, at 12:06:04PM, Andrew Francis wrote:
> Message: 1
> Date: Thu, 17 May 2012 00:58:57 +0200
> From: Louis
> Subject: [Twisted-Python] Synchronous calls using Twisted?
> To: twisted-
Thanks for the link, added to code as comment.
On Jan 12, 2012, at 10:06:16AM, Augusto Mecking Caringi wrote:
> On Thu, Jan 12, 2012 at 3:56 PM, Mike Winter wrote:
>> That helps, thanks.
>>
>> I know that http processing does \r\n, I suppose there is an rfc that says
That helps, thanks.
I know that http processing does \r\n, I suppose there is an rfc that says this
is reasonable, and LineReceiver is designed to be used in http for the same
reason.
On Jan 12, 2012, at 4:42:45AM, Itamar Turner-Trauring wrote:
> At a guess, it's because by default LineReceiv
i can telnet to the port given in test-code below and it interacts
appropriately. The connection is to a regular portforwarder and the server is
an Answer-server:
class Answer(LineReceiver):
answers = {'How are you?': 'Fine',
'no': 'No!?!',
None : "I don't know
