Hi Scott, --- "Weaver, Scott" <[EMAIL PROTECTED]> wrote: > If we used client-side operations to alter window state, how would we > maintain/persist a user's window state when that user closes their > browser? > > What if a user logs in from a different browser on a different > machine, wouldn't they expect the state of there portlets to be same > no matter where they are accessing the portal from? >
Ok, what I think is necessary is the notion of a client=side controller that would notify the server-side of the window states that were being set on the client rather than constantly reloading pages all the time. The immediate model that comes to mind is the one of using iframes for each portlet where you can declare some of these portlets at 'persistent' like a media player portlet and the controller would tell the other 'non-persistent' portlet iframes to 'reload' on certain events. This way the entire page is not reloading and destroying client-side technology contexts. rgds, Gerry Reno __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
