portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21294] - Event Model proposal
Date Fri, 04 Jul 2003 01:13:13 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21294>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=21294

Event Model proposal





------- Additional Comments From david@bluesunrise.com  2003-07-04 01:13 -------
How does this relate to the current Turbine-based Action-event framework?
Can these events be kicked off via a turbine action?
Or will we be able to address these actions in a URL, or do we have to use the existing model.
To me it seems that you are proposing an event model that co-exists with our current action-
event model inherited from Turbine. But I don't see how it addresses typical portlet actions.
Perhaps that is best, they are two separate things.

So I see this as a way for portal components to communicate, but not as a action-event system
like  
the existing system, although a action-event could kick off a 'ScopeEvent'

Looking at the diagram...
Not sure if I like this just because it confusing with the flipflop of scope and event: 

ScopeEvent
    |
    V
EventScope

that and to me a ScopeEvent would be better described as a PortletEvent since thats really
what it 
is.

Trying to understand, from your msg:
Scopes: Session, Request, Portal, Portlet Set, Portlet Group (for interportlet
communication between arbitrary groups of portlets), Portlet, Portlet Instance. 

My interpretation of the different scopes, please correct me if wrong:
1. session - is this just an arbitrary scope - meaning that a portet can subscribe to any
the event 
scope called "session". Does it have any other meaning? 
2. request - ""
3. portal - ""
4. Portlet - Does this target only one portlet? Would this event need a PortletName attribute?
5. Portlet Instance - Would we need an instance id?
6. Portlet Set - again, does this need an attribute
7. POrtlet GRoup - I see this as an arbitrary collection of portlets

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org


Mime
View raw message