OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Subject: RE: [wsia] [wsrp] [wsrp-wsia joint interfaces] Merged interfacesdocument

Supporting a batch operation mode through arrays does not seem very clean.
In the "getFragment" 
case (getFragments?), the portal will most likely then have to wait until
the whole array is 
returned (i.e. all remote portlets have rendered) before it can display the
resulting mark-up. 
How many consumer to producer parallel calls do we expect typically? I would
rather leave 
call batching up to the (future) SOAP stack.

Always using "Entity" as the thing to create remotely seem to loose the
"class" versus "object"
semantics that the WSRP "template" and "instance" operation names used to
imply. Do we now see no
no difference between remote data storage - 'templates' (possibly with
inheritance) and 
computational entities - 'instances', that WSRP seems to naturally call for?
Or are these the 
persistent v.s. transient entities of the document (for me, portlet
instances persist too)?

In trying to follow the discussion, I'm confused as to why we need both
sessions and transient 
entities, both being under the control of the consumer. I do see a need for
common sessions 
(same user/group or consumer portal) but do not see the need for other
transient entities, 
expecting a consumer to have to pay for all entities, in some way, in the
real world. I know 
the next call will discuss these but could someone give a brief rational
before then?


Andre Kramer, Citrix Systems, Inc.

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 07 June 2002 20:38
To: wsia@lists.oasis-open.org; wsrp@lists.oasis-open.org
Subject: [wsia] [wsrp] [wsrp-wsia joint interfaces] Merged interfaces

Here is a draft of the merged interfaces document that Carsten and I have
been working on this week. The largest conceptual change from the previous
0.44 Joint Spec Draft is the appearance of arrays in most of the
operations. This allows Consumers on the scale of portals to efficiently
interact with Producer services.

(See attached file: WSIA - WSRP Interface Specification.doc)

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]

Powered by eList eXpress LLC