RE: [Fwd: [wsrp-interfaces] Groups - Import

Mike,

I had a few questions/comments. If appropriate, we can discuss some of these during the conference call rather than over e-mail:

There are a few places in which you return a “reason” of type String describing a single failure during a bulk operation. Would it make sense, instead, to use the Fault type? This would allow the reuse of the faults thrown during the non bulk operations. This would lead to consistency and easier implementation.
In the first paragraph of the getPortletStates() operation, the following is stated:

“Producers that don't already return their portlets persistent state in each response carrying a PortletContext MUST be prepared to receive and handle this call. Consumers MUST only make this call for those portlets it isn't already maintaining the portletState for on behalf of the producer.”

This is a little unclear to me. Are you trying to state the following:

a. If a Producer does not use consumer side persistence, it must be prepared to receive and handle this call

b. If a Producer does use consumer side persistence, but, for a particular portlet, it has not sent portlet state to the consumer, it must be prepared to receive this call

c. A consumer must only make this call for those portlets for which it is not storing any state, whether the associated producer is using consumer side or producer side persistence.

Essentially, I’m trying to clarify the case when a producer is using consumer side persistence, but, for a particular portlet, no state has been sent.

“Consumers should be aware that calls to getPortletStates() may be costly and should break large requests into chunks. Producers are free to evaluate the cost of any given request and adjust the number of portlets it satisfies with a successful response...” This is a bit awkward, since different producers will set different limits. How does a consumer know how large a chunk is too large? Also, it doesn’t seem very useful to have a Producer spend cycles filling the response with nil values. Especially since the Consumer will either stop after the first one that fails or, if it was being very robust, spend time cycling through all of them. I would propose either of the following:

Have the producer provide a limit somewhere in the ServiceDescription. If the limit is exceeded, the Producer can throw a Fault
Simply have the producer throw a Fault. The producer can probably evaluate the number of requested responses at the start of the operation and determine that there are too many. The consumer can then act on the fault by splitting up the request.

Import – It’s not clear how this solves the case when the publishing is occurring for the second time. In other words, you’ve pushed the portlets to production, make some changes on the staging machine, and then push them to production again. It seems like the users’ customizations would be lost, since you’re creating another clone from the POP.

Scott

From: Michael Freedman [mailto:Michael.Freedman@oracle.com]
Sent: Thursday, July 01, 2004 9:47 AM
To: interfaces
Subject: [Fwd: [wsrp-interfaces] Groups - Import_Export.html uploaded]

FYI ... this is a draft strawman of the API to support import/export. We will discuss this in next Wednesdays concall.
-Mike-

-------- Original Message --------

Return-Path:	<wsrp-interfaces-return-116-Michael.Freedman=oracle.com@lists.oasis-open.org>
Received:	from rgmum3.us.oracle.com by rgmum1.us.oracle.com with ESMTP id 3918606461088699538; Thu, 01 Jul 2004 10:32:18 -0600
Received:	from rgmgw3.us.oracle.com by rgmum13.us.oracle.com with ESMTP id 1458374901088699226; Thu, 01 Jul 2004 10:27:06 -0600
Received:	from agminet01.oracle.com (agminet01.oracle.com [141.146.126.228]) by rgmgw3.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i61GSjmt013437 for <Michael.Freedman@oracle.com>; Thu, 1 Jul 2004 10:28:45 -0600
Received:	from agminet01.oracle.com (localhost [127.0.0.1]) by agminet01.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id i61GSiL0015590 for <Michael.Freedman@oracle.com>; Thu, 1 Jul 2004 09:28:44 -0700
Received:	from mail.oasis-open.org (mail.oasis-open.org [209.202.168.102]) by agminet01.oracle.com (Switch-3.1.4/Switch-3.1.0) with SMTP id i61GNK3P009548 for <Michael.Freedman@oracle.com>; Thu, 1 Jul 2004 09:24:37 -0700
Received:	(qmail 13656 invoked by uid 508); 1 Jul 2004 16:19:08 -0000
Mailing-List:	contact wsrp-interfaces-help@lists.oasis-open.org; run by ezmlm
Precedence:	bulk
X-No-Archive:	yes
List-Post:	<mailto:wsrp-interfaces@lists.oasis-open.org>
List-Help:	<mailto:wsrp-interfaces-help@lists.oasis-open.org>
List-Unsubscribe:	<mailto:wsrp-interfaces-unsubscribe@lists.oasis-open.org>
List-Subscribe:	<mailto:wsrp-interfaces-subscribe@lists.oasis-open.org>
Delivered-To:	mailing list wsrp-interfaces@lists.oasis-open.org
Received:	(qmail 13647 invoked by uid 60881); 1 Jul 2004 16:19:08 -0000
Date:	1 Jul 2004 16:25:49 -0000
Message-ID:	20040701162549.21340.qmail@pan.oasis-open.org"><20040701162549.21340.qmail@pan.oasis-open.org>
To:	wsrp-interfaces@lists.oasis-open.org
From:	Michael.Freedman@oracle.com
X-Spam-Checker-Version:	SpamAssassin 2.63 (2004-01-11) on hermes.oasis-open.org
X-Spam-Status:	No, hits=1.5 required=7.0 tests=NO_REAL_NAME autolearn=no version=2.63
X-Spam-Level:	*
Subject:	[wsrp-interfaces] Groups - Import_Export.html uploaded

The document Import_Export.html has been submitted by Michael Freedman (Michael.Freedman@oracle.com) to the WSRP Interfaces SC document repository.

Document Description:

Download Document:

http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/7534/Import_Export.html

View Document Details:

http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=7534

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.

wsrp-interfaces message