Hi Scott, --- "Weaver, Scott" <[EMAIL PROTECTED]> wrote: > > I'm assuming that there would be an 'API' so that the developer > would > > know how to talk to the proxy and request their portlet refresh. > > Developers should not need to be aware of this. We would have > configuration options that would generate URLs that would be aware of > this and possibly use javascript to intercept these requests and send > them to the proxy. Like I said I don't have all the technical > details figured out. > > We need to hide as much of the implementation as possible from the > developer so their portlets can be used in portals that support > JSR-168 but do not support the extended DOM interaction model you are > proposing. >
Something like a Refresh button would be optional and would need to be examined as to whether it could be applied to both models. Ok, I understand. You need to think about it some more for further details to emerge. 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]
