Re: [wsrp] Groups - AJAX Use Cases (ajax_use_cases.ppt) uploaded

[Rich Thompson <richt2@us.ibm.com>]

We definitely need to discuss how at
least some portion of the AJAX use cases can be addressed with v1 &
v2. My comment is that intermixing that discussion with the initial pass
to elucidate the use cases distracts from extracting the underlying issues,
particularly those that cut across all use cases.

As for UC6, there are a variety of use
cases that would want to participate in the three phase lifecycle ... this
use case appears to intermix the portlet presenting its dialog in a manner
that leverages the ability to present its markup in a popup. My comment
is that the popup issues detract from the AJAX-specific issues that we
should focus on in this discussion. However, the fact that some developers
want to do AJAX and popups would be good to note.

Rich

Subbu Allamaraju <subbu@bea.com>

05/02/06 12:08 AM

To	Rich Thompson/Watson/IBM@IBMUS
cc	wsrp@lists.oasis-open.org
Subject	Re: [wsrp] Groups - AJAX Use Cases (ajax_use_cases.ppt) uploaded

 From earlier discussions on this topic, I heard
some in the TC asking 
to see what works with 1.0 and 2.0 and what does not. So, my intent is
to see how far one can go.

I may not be getting your comment on wanting to see the base level 
issues. Could you clarify? The core issue is letting a portlet 
participate in the three-phase cycle.

UC6 is not about a traditional popup. It uses a modal dialog style that
some apps are trying to implement to simulate dialogs within a browser's
markup without opening new windows.

Subbu

Rich Thompson wrote:
> 
> I find the intermixing of the use cases with how they could be addressed
> (particularly when the proposed implementation choices aren't strictly
> limited to spec-defined semantics) distracting. I think fundamentally
> there are use cases for the Portlet getting new data, the Portlet
> getting new markup and the Consumer moving its aggregation point to
the 
> browser. The finer grained approach might help clarify the issues,
but I 
> would find it useful to discuss the base level issues first. As we
have 
> with other features, arriving at a crisp definition of the issues
before 
> looking at solution choices tends to bound the discussion better to
> result in better progress in building consensus on a solution.
> 
> I would also suggest removing UC6 entirely as it is a mixing the AJAX
> use case with the popup use case and we explicitly decided to not
> address the popup use case in v2.
> 
> You reiterate several times that Portlets do not receive several pieces
> of state on http proxied resource requests, but also note at least
once 
> that the real issue is that the Portlet has to encode that information
> into the resource URL or Portlet session for its own use when the
URL is 
> activated. Since that is the real issue, I would suggest rewording
these 
> points.
> 
> Rich
> 
> 
> *subbu@bea.com*
> 
> 05/01/06 12:45 PM
> 
>                  
> To
>                  wsrp@lists.oasis-open.org
> cc
>                  
> Subject
>                  [wsrp]
Groups - AJAX Use Cases (ajax_use_cases.ppt) uploaded
> 
> 
>                  
> 
> 
> 
> 
> 
> The document revision named AJAX Use Cases (ajax_use_cases.ppt) has
been
> submitted by Subbu Allamaruaju to the OASIS Web Services for Remote
> Portlets (WSRP) TC document repository.  This document is revision
#1 of
> ajax_use_cases.ppt.
> 
> Document Description:
> Describes several use cases using AJAX and portlets.
> 
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/wsrp/document.php?document_id=17908
> 
> Download Document:  
> http://www.oasis-open.org/apps/org/workgroup/wsrp/download.php/17908/ajax_use_cases.ppt
> 
> Revision:
> This document is revision #1 of ajax_use_cases.ppt.  The document
details
> page referenced above will show the complete revision history.
> 
> 
> PLEASE NOTE:  If the above links do not work for you, your email
application
> may be breaking the link into two pieces.  You may be able to
copy and paste
> the entire link address into the address field of your web browser.
> 
> -OASIS Open Administration
> 
> ---------------------------------------------------------------------
To 
> unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail. You may a link to this group and all your TCs
in 
> OASIS at: 
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php



---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php