Re: [wsrp-interfaces] Groups - Portlet Transport.htm uploaded

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

You are correct our solution will have to take into account large data 
sets.  Merely transferring an old registration context to a new one 
however isn't a sufficient solution.  Many of the use cases require the 
old registration to continue to run side by side with  the new 
registration as well as to only transfer only a subset of the portlets 
managed by the producer/registration.
     -Mike-

Subbu Allamaraju wrote:

>
> If I understand this proposal correctly, the primary use is to be able 
> to transfer (via an export and import) portlet persistent state 
> associated with one registration context to another. If the persistent 
> state is large enough, it could take down the producer or the network. 
> This seems very expensive to me. Instead, it would be much simpler if 
> the producer is allowed (by updating the semantics of registration, or 
> via a new operation) to associate the old registration context with 
> the new.
>
> Subbu
>
> Michael.Freedman@oracle.com wrote:
>
>> The document revision Portlet Transport.htm has been submitted by 
>> Michael Freedman (Michael.Freedman@oracle.com) to the WSRP Interfaces 
>> SC document repository.
>> This document is revision #1 of Portlet Transport.htm.
>>
>> Document Description:
>>
>>
>> Download Document: 
>> http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/5525/Portlet%20Transport.htm 
>>
>>
>> View Document Details:
>> http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=5525 
>>
>>
>> Revision:
>> This document is revision #1 of Portlet Transport.htm.  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.
>>
>>