OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: [wsrp-wsia] [change request #142] Remove performInteraction() ?



Although I really like the performInteraction operation since it is a nice
optimization, if we don't need it anymore to support the JSR we should
remove it from WSRP 1.0 nevertheless for the following reasons:

- It adds complexity - one additional operation
   -> adding to the complience test suite
   -> adding effort to compliance test execution
   -> adding effort to interop test execution
   -> adding complexity to consumer and producer implementations
   -> increasing the risk of non-interoperability of implementations from
different vendors

I think it is better to have a simple V 1.0 spec for which we can create
interoperable implementations without too many complexities and testing
effort than to have more bells and whistles rasing complexity and moving
out the date where we can achieve cross vendor interoperability.

Best regards,

Thomas



|---------+---------------------------->
|         |           Andre Kramer     |
|         |           <andre.kramer@eu.|
|         |           citrix.com>      |
|         |                            |
|         |           02/13/2003 12:57 |
|         |           PM               |
|         |                            |
|---------+---------------------------->
  >------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                              |
  |       To:       wsrp-wsia@lists.oasis-open.org                                                                               |
  |       cc:                                                                                                                    |
  |       Subject:  RE: [wsrp-wsia] [change request #142] Remove performInteraction()       ?                                    |
  |                                                                                                                              |
  >------------------------------------------------------------------------------------------------------------------------------|




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.

regards,
Andre

-----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>






[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC