Path: csiph.com!usenet.pasdenom.info!gegeweb.org!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!cs.uu.nl!news.stack.nl!newsfeed.xs4all.nl!newsfeed4.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Newsgroups: comp.lang.python
Date: Sun, 14 Apr 2013 19:41:39 -0700 (PDT)
In-Reply-To: <mailman.609.1365981993.3114.python-list@python.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=123.192.32.215; posting-account=5JdMBQoAAABHnS4mjpqEzxnmWtgiiVNw
References: <mailman.609.1365981993.3114.python-list@python.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Subject: Re: Threadpool item mailboxes design problem
From: 88888 Dihedral <dihedral88888@googlemail.com>
To: comp.lang.python@googlegroups.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: python-list@python.org
Precedence: list
Message-ID: <mailman.617.1365993702.3114.python-list@python.org>
Lines: 75
NNTP-Posting-Host: 2001:888:2000:d::a6
Xref: csiph.com comp.lang.python:43600

Charles Hixson=E6=96=BC 2013=E5=B9=B44=E6=9C=8815=E6=97=A5=E6=98=9F=E6=9C=
=9F=E4=B8=80UTC+8=E4=B8=8A=E5=8D=887=E6=99=8212=E5=88=8611=E7=A7=92=E5=AF=
=AB=E9=81=93=EF=BC=9A
> What is the best approach to implementing actors that accept and post=20
>=20
> messages (and have no other external contacts).
>=20
>=20
>=20
> So far what I've come up with is something like:
>=20
> actors     =3D {}
>=20
> mailboxs =3D {}
>=20
>=20
>=20
> Stuff actors with actor instances, mailboxes with multiprocessing.queue=
=20
>=20
> instances.   (Actors and mailboxes will have identical keys, which are=20
>=20
> id#, but it's got to be a dict rather than a list, because too many are=
=20
>=20
> rolled out to disk.)  And I'm planning of having the actors running=20
>=20
> simultaneously and continually in a threadpool that just loops through=20
>=20
> the actors that are assigned to each thread of the pool.
>=20
>=20
>=20
> This lets any actor post messages to the mailbox of any other actor that=
=20
>=20
> it has the id of, and lets him read his own mail without=20
>=20
> multi-processing clashes.  But I'm quite uncertain that this is the best=
=20
>=20
> way, because, if nothing else, it means that each mailbox needs to be=20
>=20
> allocated large enough to handle the maximum amount of mail it could=20
>=20
> possibly receive.  (I suppose I could implement some sort of "wait=20
>=20
> awhile and try again" method.)  It would, however, be better if the=20
>=20
> mailbox could be specific to the threadpool instance, so less space=20
>=20
> would be wasted.  Or if the queues could dynamically resize.  Or if=20
>=20
> there was a threadsafe dict.  Or...  But I don't know that any of these=
=20
>=20
> are feasible.  (I mean, yes, I could write all the mail to a database,=20
>=20
> but is that a better answer, or even a good one?)
>=20
>=20
>=20
> --=20
>=20
> Charles Hixson

Actors can receive and response to messages to take actions
accordingly in time in one or more cores.

The timer is required and the message read/write operations=20
are required.

Do you want the actors to gain new methods to evolve=20
in the long run?