[Pharo-project] Announcement real problems - please read and comment.

Denis Kudriashov dionisiydk at gmail.com
Sat Apr 2 09:46:31 CEST 2011


2011/4/2 Stéphane Ducasse <stephane.ducasse at inria.fr>

> Henrik what is your answer to problem 1
> Problem 1
>        - the second announcement was never sent, because the first one
> broke the second was blocked.
>        >> we should make sure that if an announcement leads to an error,
> other annoucements on the same emit should pass
> Because we can get the system down just because one guy can register a bug.

I have similar problems in my domain. And my solution is asynchronous
announcer. Each announcement  subscriber should be notified in separate
process. It is very easy to implement
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gforge.inria.fr/pipermail/pharo-project/attachments/20110402/b0d2a09c/attachment.htm>

More information about the Pharo-project mailing list