[Zope-PTK] portal_events

[Paul Everitt]

This would also match the XML DOM Level 2 model:

"""
The _EventListener_ interface is the primary method for handling events.
Users implement the EventListener interface and register their listener
on an _EventTarget_ using the _AddEventListener_ method.
"""

--Paul

> -----Original Message-----
> From: Shane Hathaway [mailto:hathawsh@yahoo.com]
> Sent: Wednesday, August 23, 2000 6:02 AM
> To: webmaven@lvcm.com
> Cc: zope-ptk@zope.org
> Subject: [Zope-PTK] portal_events
> 
> 
> Michael,
> 
> portal_events would consist of only a small piece of
> code, would not require any change to existing
> architecture, and would not introduce a dependency on
> ZPatterns.  It would be an implementation of a common
> design pattern.  So no, it's not a duplication of
> ZPatterns agents.
> 
> However, your message and Andrew Wilcox's reminded me
> of the change to the event model in the transition
> from JDK 1.0 to JDK 1.1.  In 1.0 you had to subclass
> to receive events.  In 1.1 you have to subscribe to
> receive very specific events.
> 
> portal_events, as proposed, would let you subscribe to
> *all* portal events.  Maybe instead of that approach
> we need to add event subscription capability to
> specific tools, such as:
> 
>   portal_workflow.addStatusChangeListener()
> 
> and:
> 
>   portal_workflow.removeStatusChangeListener()
> 
> What does everyone think of that?  It would match the
> Java model, making it not only familiar but proven to
> work.
> 
> Shane
> 
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Mail - Free email you can access from anywhere!
> http://mail.yahoo.com/
> 
> _______________________________________________
> Zope-PTK maillist  -  Zope-PTK@zope.org
> http://lists.zope.org/mailman/listinfo/zope-ptk
> 
> See http://www.zope.org/Products/PTK/Tracker for bug reports 
> and feature requests
>