portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Matthew Forsyth <andaluc...@yahoo.com>
Subject qualified parameters
Date Fri, 04 Oct 2002 23:31:40 GMT
In Oracle Portal, portlet-developers are expected to
make use of a method named something like

getQualifiedParameter(String paramName)

and when generating url's, they generate parameter
names using something like

addQualifiedParameter(String paramName)

what these do is to take a parameter name and add the
portlet id onto it before interacting with the actual
http parameters...  

This is good practice because it prevents the chaos of
2 unrelated portlets on the same page (or 2 instances
of the same portlet) using the same parameter name. 
Since in web apps all portlet-specific commands are
sent/received using the single set of request
parameters, this is a major issue, especially if
portlets are going to be sold/distributed to other
peoples' portals.

Do you think Jetspeed would benefit from this
approach, and if so, to what part of the om should
these methods be added?  

In general, is there ever an advantage to allowing
unqualified parameters?  I can't think of a reason I
would ever use a regular parameter in a portlet, if
qualified parameters were a part of the api.


Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!

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

View raw message