[Arp] Central dispatcher
chris.velevitch at gmail.com
Wed Apr 20 06:17:42 PDT 2005
On 4/20/05, Aral Balkan <aral at ariaware.com> wrote:
> >I disagree. Just because both forms know about an events of type X
> >does not imply the forms explicitly knows about each other.
> Well, if you have to listen for an event on an object, you must know
Why are you tying an event to an object? What's wrong with an event
being unique and independent? Certainly, some events may only ever get
generated from one specific object, but surely dealing with event is
truly independent of the object the generated it?
> about that object and that means that you have a reference to the
> object. This creates dependencies. Whether or not these dependencies are
> desirable (or even avoidable), of course, depends on the specifics of
> the situation.
Surely these dependencies only exist because the current ARP event
model is too simplistic? Needing a reference to an object that
generated the event, to me, implies that additional information is
needed by the object receiving the event. So, I would think that the
event would need to include that additional information. Thus making
processing of the event independent of the object generating the
More information about the Arp