[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [wsrp-wsia] [change request #142] Remove performInteraction() ?
Currently the consumer will only initiate a non-blocking interaction if the developer constructs a non-blocking action URL and writes it to a markup fragment. Unless I'm missing something, this means the API and Portlet developers can ignore the extra protocol complexity. One possibility is that a renderURL used as a html FORM target url gets translated to a performInteraction by the consumer. Then we would need to expose the non-blocking case to the developer or, say, make input available in the JSR 168 render(). This then seems to be my main remaining use case for non-blocking actions: indicating redirect and mode and other state changes are not possible at the consumer while posting data. regards, Andre -----Original Message----- From: Subbu Allamaraju [mailto:subbu@bea.com] Sent: 13 February 2003 19:14 To: wsrp-wsia@lists.oasis-open.org Subject: Re: [wsrp-wsia] [change request #142] Remove performInteraction() ? Andre Kramer wrote: > Portlet developers need not see perform(non-blocking)Interaction (as in JSR > 168). One thing we can't do with render URLs / getMarkup is post form data. > Or have complex inputs generally, which seems a bit of a hole in our 2 op > model. I'm not sure if portlet developers won't be required to see this. Irrespective of the programming model used (JSR168 or something else), I think portlet developers will have to be aware of blocking-vs-nonblocking semantics, and declare if a portlet is capable of non-blocking interactions or not. Don't you think so? Regards, Subbu > -----Original Message----- > From: Subbu Allamaraju [mailto:subbu@bea.com] > Sent: 12 February 2003 17:27 > To: wsrp-wsia@lists.oasis-open.org > Subject: Re: [wsrp-wsia] [change request #142] Remove > performInteraction()? > > > I vote for the "less is more" argument. One less complex concept to > understand and program to for portal developers! > > Subbu > > Rich Thompson wrote: > >>Document: Spec >>Section: 6.3.1 >>Page/Line: 40/18 >>Requested by: Mike Freedman >>Old text: >>New text: remove performInteraction() >>Reasoning: This operation was originally added to provide some semantics >>defined by JSR 168. JSR 168 has redefined itself in such a way that this >>operation is no longer needed [by it]. Hence we can consider dropping it. > > >> Noet: Personally, I am torn about dropping it. Though JSR 168 doesn't >>expose/need it [yet], I think the semantics are well defined, clear, and >>useful. I believe that many portlets wanting optimal page rendering >>performance can use "non-blocking" actions to post portlet internal data >>to themselves. The only argument I see for getting rid of it [now that it > > >>is defined] is "less is more" i.e. the specification is easier to >>understand if there are fewer concepts. I can buy this but would find it >>silly if this operation was added back in 1.1 or 2.0 when it could have >>been in 1.0. >> >>[RT] I also do not see compelling reasons to drop it at this point. It >>does add useful semantics and they are well defined in the spec at this >>point. The concepts involved have to be understood by Consumer >>implementors and therefore will not disappear from the spec. >> >>---------------------------------------------------------------- >>To subscribe or unsubscribe from this elist use the subscription >>manager: <http://lists.oasis-open.org/ob/adm.pl> > > > > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC