RE: [wsrp-interfaces] New Import Export document

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

As you point out, a scenario reminiscent
of capturing a version in a source library is a manner of capturing a snapshot
without the potential for massive amounts of data traversing the network.
We should consider it as an alternative, my first questions/thoughts are:

1. Does use of a SnapshotRegistration
provide the flexibility in the export/import proposal for either sending
the data needed to produce a clone of a portlet to the Consumer or just
a reference to this information? My first guess is 'yes' as the portletState
can be pushed to the Consumer.

2. Does managing this special class
of registrations (would they be a special class or is it merely a use of
the registration concept by the Consumer?) cause any particular burden
on Producers?

3. How does a Producer who does not
support registrations provide the equivalent function?

Rich

Andre Kramer <andre.kramer@eu.citrix.com>

07/22/2004 09:44 AM

To	Rich Thompson/Watson/IBM@IBMUS
cc
Subject	RE: [wsrp-interfaces] New Import Export document

I definitely was not attempting
to solve the cross-producer migration issues only to show that they could
be supported by a "by-reference" style operation too. If one
allows different flavors of "registrations" to be created then
a consumer could, e.g., create a new registration (handle) as an archive
or storage area and copy portlets into this registration (a sort of "export")
and then copy again later, on to a 3rd registration to "import"
the portlets again. Any such semantics would be negotiated out of band
as you suggest (by asking for different "types" of new registrations,
as supported by producers, for example). But the question I had question
is whether a consumer initiated direct copy within in producer (across
registrations) solves the basic deployment management use cases?
 
Regards,
Andre

---

From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 22 July 2004 14:26
To: interfaces
Subject: RE: [wsrp-interfaces] New Import Export document
 

The main difference I see between such an operation and the proposed export/import
is that the operation references the current state of a portlet while export/import
proposal captures a snapshot and then looks to recreate it. For some of
the use cases, I think this is an important difference.

I would suggest we not get involved in scenarios involving a migration
of the Producer as well. How would a Consumer, in general, learn the following
scenario relative to Portlets exported from Producer1:
- PortletA may be imported to Producer 2, but not Producer3
- PortletB may be imported to Producer3, but not Producer2
- None of the exported portlets may be imported to ProducerN

With the opaque nature of exportedState, Producers can easily store enough
information to allow automation of such cross-Producer (same vendor implementation)
imports. Out-of-band communication to the Consumer of which portlets a
different Producer is able to import seems appropriate for our protocol
(at least until other deployment protocols get defined that we could leverage).

Rich

Andre Kramer <andre.kramer@eu.citrix.com>

07/22/2004 06:45 AM

To	"'Michael Freedman'" <Michael.Freedman@oracle.com>, interfaces <wsrp-interfaces@lists.oasis-open.org>
cc
Subject	RE: [wsrp-interfaces] New Import Export document

 

As Exporting / Importing state has privacy and reliability issues, how far would the following operation go in covering the use cases?
 
PortletHandle newHandle = copyPortlet(PortletHandle thePortlet, RegistrationHandle fromRegistration, RegistrationHandle toRegistration);
 
This would normally be called by a wsrp consumer (e.g. when a staged deployment goes live). I've purposely not included our portletState to show that no data need be passed outside of the producer(s). Two producers could pass portlet data between themselves (using a proprietary API or the proposed Export/Import mechanism) if the registrations are on different producers.
 
Regards,
Andre
 

 

---

From: Michael Freedman [mailto:Michael.Freedman@oracle.com] 
Sent: 22 July 2004 01:46
To: interfaces
Subject: [wsrp-interfaces] New Import Export document
  
I have rewritten the original strawman to define specific import/export
methods.  It has been uploaded
to the Interfaces documents.
 If you want to refer to the old version click on "Manage"
to the far right of the document entry.  This takes you to a page
where you can see the previous revision(s). 
    -Mike-