asynchat and threading

[Anthony Baxter]

Re: asynchat and threading

On Mon, 29 Nov 2004 23:24:54 -0500, Caleb Hattingh <caleb1@telkoms a.net> wrote:[color=blue]
> I heartily support something like this, but alas I have not the time to
> help out with it. I like the Enthought python distribution because it
> installs several packages in one shot. A pity there isn't a similar thing
> for python addons in Linux (or is there?).[/color]

Plenty of people would like to see this. Alas, no-one has stepped forward
to do the work (or, if you have money but no time, to offer to fund the work).

Python runs on volunteers - no-one's done this yet, so it's not happened.

[Fredrik Lundh]

Re: asynchat and threading

Anthony Baxter wrote:
[color=blue][color=green]
> > AFAICT, the main complaint is that it is tied to the TCP transport,
> > the sockets API, and the select/poll API. IOW, it cannot easily:
> > - integrate TLS on top of TCP (because TLS might involve no-data
> > communications, e.g. when TLS negotation happens in the middle
> > of a TLS session),
> > - integrate other transports, such as serial ports on Windows,
> > - integrate other multi-endpoint wait APIs, such as IO completion
> > ports on Windows NT+, or kqueue on BSD.[/color]
>
> - work with other event loops, such as GUI toolkits[/color]

sure can.

but sure, if you don't want it to work, nothing stops you from writing
crappy code. we've been using asyncore/medusa on high-performance
servers for nearly 10 years; I think we'd noticed by now if the library
was seriously broken.

</F>