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 Mon, 07 Jul 2003 21:19:53 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 tkuebler@cisco.com  2003-07-07 21:19 -------
This is not an event model for portlets, but for a portal in total.   Purhaps
the best way to imagine it is as awt component event model applied to the entire
portal page. The portlet event is one of the component events serviced by this,
but there are also page events, etc.  The event scope talked about here (purhaps
misnamed) is roughly mapped to a portion of the portal page or http request cycle.

I'll try to get a couple of use cases and diagrams together after I finish
getting the GenericMVCPortlet cleaned up and the caching working.

The idea here is to bring the awt component event model into a portal context
since people look at a portal page with all it's window controls and such in
that light.

---------------------------------------------------------------------
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