[Dev] Comments about Threading Summary
andrewfr_ice at yahoo.com
Tue Oct 28 13:50:09 PST 2003
I read the Threading Summary. Some comments.
> We should do code reviews of threading code,
>including: repository, agents, notification
>framework, worker parcels
Well, you should do serious reviews of all code....
I review parts of the agent framework and provide
feedback. That said, the Notification manager
was designed with thread-safety and deadlock
avoidance in mind. In this regard, the code
takes a conservative approach. I still occasionally
look over the code for mistakes and am researching
ways of making the NM more efficient.
It strikes me that Chandler's concurrency model
is too tightly tied to a specific thread
implementation. Perhaps this is okay in the short
term and maybe even unavoidable to get work done.
I am a newie to Python. However I am reading about
interesting developments in regard to co-routines
and continuations that a future Chandler concurrency
model may want to leverage.
Notification Manager and Interprocess Communications:
It would be relatively easy to use the NM for
interprocess communications. This may have to
be done. I have thought about methods like:
send(), receive(), and reply() for asynchronous
and synchronous communications (the Sun 4.1
LWP library had these functions. And I believe
Mach IPC has similar functions).
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
More information about the Dev