On 10/10/06, Josiah Carlson <[EMAIL PROTECTED]> wrote:
> > the really interesting thing here is a ready-made threading-style API, I
> > think.  reimplementing queues, locks, and semaphores can be a reasonable
> > amount of work; might as well use an existing implementation.
>
> Really, it is a matter of asking what kind of API is desireable.  Do we
> want to have threading plus other stuff be the style of API that we want
> to replicate?  Do we want to have shared queue objects, or would an
> XML-RPC-esque remote.queue_put('queue_X', value) and
> remote.queue_get('queue_X', blocking=1) be better?

Whatever the API is, I think it is useful if you can swap between
threads and processes just by changing the import line.  That way you
can write applications without deciding upfront which to use.
_______________________________________________
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Reply via email to