Re: [wsrp-interfaces] Deployment

Ah, I didn't mean to make my questions sound so producer specific. I am more
trying to solve how to move portlet assets across producer installations. If
the solution is to push the configured portlet assets to the consumer and
have it import it to another producer, that sounds fine.

I assume for the second case that the export of the subset of cloned portlets
would contain any state the producer is maintaining for those cloned portlets?

Also, what do you mean when you say that the consumer would register with an
identical deployment of the origin producer? Is this to say that we would
allow a way for the consumer to register with a different producer yet specify
its registration context, or would the registration context simply be "imported"
after a registration with the new producer?

Thanks,
Christopher


Christopher Coco
Senior Software Engineer
Vignette Application Builder
p. 415.995.3534 | f. 415.975.9801

Vignette's software and expertise help organizations harness 
the power of information and the Web to deliver measurable 
improvements in business efficiency. Vignette is the efficiency 
expert. Visit http://www.vignette.com/ to learn more. 



-----Original Message-----
From: Michael Freedman [mailto:]
Sent: Thursday, April 29, 2004 7:43 AM
To: Coco, Christopher
Cc: 
Subject: Re: [wsrp-interfaces] Deployment


WSRP is focused on defining the protocol between a consumer and a 
producer.  Though there are a number of producer specific deployment use 
cases I do think they are outside the realm of WSRP.  For example I 
don't think we will define an exportProducer function.  

As for your specific use cases:
(1)  Though the current use case limits itself to the same producer, it 
need not do so.  Its reasonable for us to expand this use case [or add 
an additional] where its a different producer deployment.  Though, in 
fact the second use case covers this, and presumably once solved is 
available for use in the first use case.  Bottom line, our solution 
needs to allow a consumer to export a producer and import into another 
deployment of that producer.  

(2)  Currently, I envision the following: consumer asks producer to 
export [a subset] of the cloned portlets from its registration.  The 
consumer migrates to another machine.  The new consumer registers with 
an identical deployment of the origin producer.  The consumer asks this 
producer to import into its registration the exported portlets its 
received from the origin producer.  [I am leaving out a lot of details 
-- like representations, etc so focus on the process].  So in the end 
deployment is only about import/exporting portlets not consumer metadata.

     -Mike-

Coco, Christopher wrote: