[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-interop] Groups - WSRP Interop SC call modified
-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: 17 July 2003 18:36
To: wsrp-interop@lists.oasis-open.org
Subject: RE: [wsrp-interop] Groups - WSRP Interop SC call modified
Sorry my notes weren't clearer.
1a) We thought it would be useful to have a convention for a value to use in this common case. We preferred to take it from the wsrp namespace, but a convention can not define new values for a namespace. As a result we have an odd, but reasonable value for the convention.
3b) Apparently I wasn't clear enough. As an optional element, the MarkupContext can be missing. Some implementation may prefer to actually send it as a nil element. In both cases, this will stimulate the Consumer to invoke getMarkup. Returning a non-nil MarkupContext will be taken as having provided the markup for this user interaction.
4bi3) Yes, the Producer may throw an OperatioFailed fault. In no case is it sensible for a Consumer to presume that the persistent state of a POP may be written. Specifying this will likely return normally when no persistent state change was attempted and return a fault when a state change is attempted.
Rich Thompson
Andre Kramer <andre.kramer@eu.citrix.com> 07/17/2003 01:15 PM
To: wsrp-interop@lists.oasis-open.org
cc:
Subject: RE: [wsrp-interop] Groups - WSRP Interop SC call modified
Apologies for joining late on the the call.1a - the convention of userContextKey="wsrp:minimal" is weird, but it's just a convention, right? Some systems have a guest system group that can be used as the basis for a real userContextKey.
I don't understand 3.b:
"The signal for getting getMarkup called is a nil MarkupContext or missing." - or missing what? Could it be missing mimetype? I would like to be able to return a new preferredTitle with and without markup from pbia. Also, in future we may be passing back a CacheControl without markup.4 b(producer side) i(POP being accessed) 3(PortletStateChange=readWrite -> make no sense, throw OperationFailed)
- in the general case this is just: "the producer may throw an Operation failed".
i.e. only makes "no sense" for JSR portlet?My question is: how does a non-JSR168 portlet know that POP readWrite is not allowed? We don't expect it to catch OperationFailed and retry with readOnly do we?
thanks,
Andre-----Original Message-----
From: richt2@us.ibm.com [mailto:richt2@us.ibm.com]
Sent: 17 July 2003 17:35
To: wsrp-interop@lists.oasis-open.org
Subject: [wsrp-interop] Groups - WSRP Interop SC call modified
WSRP Interop SC call has been modified by Rich Thompson (richt2@us.ibm.com).
Event description:
Shared timeslot with Conformance SC and biweekly TC call.
USA Toll Free Number: 877-718-0936
USA Toll Number: +1-712-923-6878
PARTICIPANT PASSCODE: 402957Agenda:
Date: Thursday, 17 July 2003
Time: 11:00am - 01:00pm Eastern TimeThis event is one in a list of recurring events.
Other upcoming dates include:Thursday, 24 July 2003, 11:00am to 01:00pm Eastern Time
Thursday, 31 July 2003, 11:00am to 01:00pm Eastern Time
Thursday, 07 August 2003, 11:00am to 01:00pm Eastern Time
Thursday, 14 August 2003, 11:00am to 01:00pm Eastern Time
Thursday, 21 August 2003, 11:00am to 01:00pm Eastern Time
Thursday, 28 August 2003, 11:00am to 01:00pm Eastern Time
View event details:
http://www.oasis-open.org/apps/org/workgroup/wsrp/wsrp-interop/event.php?event_id=2503PLEASE NOTE: If the above link does 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.Referenced Items
Date Name Type
---- ---- ----
17 Jul 2003 20030717 WSRP Interoperabil... Minutes
You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/wsrp-interop/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]