A Minimally Server-coupled Example Background: What is different with the JSR-168 portlet specification as compared to other specifications is that the portlet specification is laying out a server-coupled view interaction model that developers and users must utilize with regard to web pages. Portlets are server-generated web page markup elements. Web page elements become part of a document object model (DOM) in the browser and can be controlled in a number of ways. Usually they are controlled by client-side technologies such as DHTML, Javascript, Flash, SVG, etc. JSR-168 as written currently prescribes that portlets are controlled via the server so every user view action with regard to the portlet results in a request back to the server. This continually destroys the DOM and any context that you may have had under DHTML, Javascript, Flash, SVG, etc.
Use the Best Tools for the Job To create an efficient portlet model, Java will need to dovetail with client-side technologies that users are currently embracing: DHTML, Javascript, SVG, Flash, etc. A Minimally Server-coupled Model In my proposal: Jetspeed View Interaction Model, the view interaction model that I believe represents the most efficient and usable model is a minimally server-coupled model that permits portlets to be generated by a Java portlet container and to be controlled on the client by any number of popular client-side technologies such as DHTML, Javascript, SVG, Flash, etc. This is a model that places functionality in the location where it is most efficient from the perspective of the Web architecture model. For efficient operation, the Web model requires that communication between web-clients and servers be kept to a minimum. There is no guarantee of network performance on the Web and the vast majority of connections worldwide are dialup via modem. So of necessity you optimally want to perform as much activity as possible on the web-client without issuing unnecessary requests to the server. Simple Example Consider this simple example of how Java might dovetail with client-side technologies to create an efficient portlet model: Envision a PC user accessing a portal page. The Java portlet container would assemble the page from portlets that are all CSS <div> elements. Once in the browser when the user clicks on a portlet to maximize it then some local client-side technology maybe DHTML maybe Flash maybe SVG reads the DOM, figures out the screen real estate, moves the portlet's CSS <div> element to a higher layer and sets its width and height attributes to 100% and it covers the entire screen. The portlet has content elements. The portlet or perhaps the content elements themselves notice that there is now have enough screen real estate for them to display and these additional elements then reveal themselves. The portlet is nearly instanteously maximized with enhanced content and none of this required a trip to the server. Additionally the user can now maximize, normalize, and minimize the portlet as many times as they like all without any requests being sent to the server. The portal can now even operate in an offline mode, the DOM integrity has been maintained, portlets such as Jetspeed's IFramePortlet function properly, and the user is experiencing near instanteous response from the user interface. Gerry Reno --- Gerry Reno <[EMAIL PROTECTED]> wrote: > There are a number of good client-side technologies that can be > used. > The problem is that they work best and sometimes only if the DOM > stays > loaded. If pages are constantly being reloaded this ends up > destroying > and recreating the DOM. > > Gerry Reno > > --- [EMAIL PROTECTED] wrote: > > > -----Original Message----- > > > From: Weaver, Scott [mailto:[EMAIL PROTECTED] > > > > > > Can svg do as much as Flash can, like Flash Forms, etc? I > > > ask this because I know very little about the current state of > svg. > > > > > > > This probably starts to get a little far afield for the Jetspeed > > list, but > > you ought to take a look at: > > http://www.kevlindev.com/index.htm - some nice basic tutorials > > http://www.visionmonster.com/svg/index.php - some artsy examples > > http://www.w3.org/Graphics/SVG/Overview.htm8 - The W3C site. > > > > I don't know anything about Flash's forms, but you can mix HTML > forms > > and > > SVG together on one page. Version 1.2 of the SVG draft just came > out > > that > > includes arbitrary XML rendering, text flowing, and some other new > > stuff. > > Adobe has a new beta version of their viewer plug-in that adds new > > features, > > too. > > > > If the Jetspeed team is thinking of adding more graphical UI stuff, > > SVG is > > definitely worth taking a long look at. > > > > - Jasen. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
