-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 02 June 2008 18:12 pm, Peter Dimov wrote:
Frank Mori Hess:
I didn't mention it, but I was thinking of a scheduler picking method requests and dispatching them using a single thread.
Hm. Are you envisaging a concurrency model in which every active_function runs its own scheduler thread? I probably need to take a look at the source of libpoet.
By default they do. They can also share a scheduler, so you can have an active object consisting of a bunch of active_functions all sharing one scheduler. That gives some automatic thread safety since all the user code run by the active_functions sharing the scheduler is run in the same thread. If each active_function corresponds to a method on an underlying ordinary object, then methods of the underlying object can all access and modify the object's internal data without worrying about concurrent access, since they will all be running in the same thread. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFIRJjX5vihyNWuA4URAphWAJ9HgIFSOB7m5HZM7CKsq+rUUf/mCQCdFVO8 5BrfuXTZsOc07MX7uT7d7UM= =nBzZ -----END PGP SIGNATURE-----