Re: [wsrp-comment] Public Comment

[Michael Freedman <michael.freedman@oracle.com>]

The situation isn't black or white with regards to WSRP 2.0 Ajax 
support.  With the addition of the getResource function WSRP 2.0 can be 
used to support a significant number of the portlet/ajax use cases.  
Where things mostly break down is when portlets want to use wsrp 2.0 
coordination features in response to their Ajax requests.  We don't 
currently support this and consider it a complex problem needing 
thinking/design/reflection to get done properly.  The first committee 
draft for wsrp 2.0 is either already posted or will be shortly.  Could 
you review our getResource support and satisfy yourself/us that though 
unstated as a goal or purpose it can be used to implement a variety of 
Ajax use cases?
    -Mike-

Subbu Allamaraju wrote:

> I'm a member of both the JSR286 EG and the WSRP TC, but these are my 
> personal comments.
>
> For the portlet API, there is a significant interest in supporting 
> Ajax use cases, and these may get solved.
>
> However, since WSRP 2.0 is in the final stages, unless there is strong 
> need felt within the TC and a much stronger feedback from the 
> community, changes to support Ajax use cases may not happen. The 
> review period for the WSRP 2.0 spec should help get feedback from the 
> community on this question.
>
> Regards,
>
> Subbu
>
> comment-form@oasis-open.org wrote:
>
>> Comment from: metek@touchtonecorp.com
>>
>> Scary thought indeed, but a real possibility. If WSRP v2 doesn't 
>> support AJAX-like methods, I hope Java Portlet Spec 2.0 will. If Java 
>> Portlet Spec 2.0 supports AJAX, but WSRP v2 doesn't, then I will 
>> personally forget about WSRP since it would be an outmoded spec. Java 
>> Portlet Spec 2.0 provides an open plug-in architecture too, within 
>> the realms of Java. If Java Portlet Spec 2.0 doesn't support AJAX 
>> too, too bad for the whole industry.
>>
>> Thank you,
>> Mete Kural
>>
>> Terry Vail wrote:
>>
>>>> A scary thought that the standard will fall by the wayside. It will 
>>>> still take something like it to achieve the true openness of "plug 
>>>> in" portlets because the current trend of "mashups" requires 
>>>> proprietary APIs. That's just what WSRP eliminates.
>>>>
>>>>  
>>>>
>>>>  
>>>>
>>>> Terry Vail
>>>>
>>>> CTO, Director of Software Development
>>>>
>>>> VitalThought
>>>>
>>>> mailto: r.terry.vail@vitalthought.com
>>>>
>>>> www.vitalthought.com
>>>>
>>>> Office: 281-535-9595 x15
>>>>
>>>> Cell: 832-577-1254
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: wsrp-comment-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: wsrp-comment-help@lists.oasis-open.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsrp-comment-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsrp-comment-help@lists.oasis-open.org
>