tismer at tismer.com
Thu Oct 10 10:03:05 CEST 2002
Eric van Riet Paap wrote:
> It's the fact that chan.send() is followed by another chan.send(),
> that's what I mean by hardcoded. What I would prefer to do is send to
> all current receivers. something like:
> for i in range(chan.numberOfCurrentReceivers):
Yep, bt the qustion is *what* you want to send.
This version of send() is meant to send a specific
value to one receiver.
If there is no specific message, just the fact that you
are sending, things are different.
> chan.sendall() #or chan.broadcast()
Broadcast will be implemented, soon.
This will also serve as a notification
mchanism. Broadcasting does not block.
It sends just once the same message to all
receivers in the chain.
> I have looked at the docstrings to see if this information is available
> but I couldn't find it. I, for a moment, thought channel.queue would be
> what I was looking for!
The queue contains all senders or receivers which
have not been satisfied yet.
This works with broadcast as well.
At the moment my priorities are different since
I'm porting for IronPort. Shortly after, these
things will be addressed in depth.
thanks for your interest - chris
Christian Tismer :^) <mailto:tismer at tismer.com>
Mission Impossible 5oftware : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34 home +49 30 802 86 56 pager +49 173 24 18 776
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/
Stackless mailing list
Stackless at www.tismer.com
More information about the Stackless