2009/11/1 Igor Stasenko <siguc...@gmail.com>:
> 2009/11/1 Lukas Renggli <reng...@gmail.com>:
>>> Another question , which Stephane noted already, is the overhead of
>>> broadcasting.
>>
>> First of all, announcements are magnitudes faster than the ancient
>> change-update and trigger frameworks.
>>
>
> i having zero interest in ancient stuff. This topic is about announcements.
>
>> The problem of broadcasting does not apply to announcements, because
>> the observer only registers and receives events he is interested in.
>>
> nope. this problem applies to announcements as well. As soon as you
> having multiple subscribers
> listening for same event, sending this event to all of them is called
> broadcasting.
> Please tell me if this definition is wrong.
>
> But in addition, announcer also iterates even over those subscribers
> who would never want to receive some announcements.
> I thought that Stephane talking about this overhead, not about some
> dusty, ancient code which i never seen.
>

Igor, even if you open a shiny new Pharo image, I'm afraid you'll have
to contemplate plenty of ancient code.
Note sure the most ancient the most dusty though ;).

FIY, st80 MVC was broadcasting to 99% of ignorers with a long chain of
this kind:
self changed: aSymbol SENT FROM THE MODEL
-> self changed:with:
--> self changed:with:from:
---> update:with:from: BROADCAST IN EACH dependents (each subview was
potentially)
--> update:with:
-> update:

I hope we don't replicate this scheme, I had understood Announcements
did not thanks to explicit subscription.
Anyway, a bit of archeology is always helpfull when cleaning Smalltalk...

Nicolas

>> Please read the blog posts of Vassily.
>>
>
> Thanks, i'm already read his blog.
>
>> Lukas
>>
>> --
>> Lukas Renggli
>> http://www.lukas-renggli.ch
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to