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


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-interfaces message

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

Subject: Re: [wsrp-interfaces] Client Attributes

1. I do think the requirements introduced in 6.1.10 & 6.1.16 will be untestable. As I went to write it, I also realized that a MUST statement would likely place an unintended requirement on the HTTP proxy case; namely, passing the additional data which the in-protocol method supplies.

2. While the Consumer is required to support both means of getting a resource, that doesn't mean that both will be supported by the Producer for any given resource.


Michael Freedman <michael.freedman@oracle.com>

02/08/2007 05:48 PM

Re: [wsrp-interfaces] Client Attributes

Thnaks.  This looks great!  Two questions:
1) You choose SHOULD over MUST -- is this because you don't think its testable?  Why does the consumer need the flexibility to have the in-protocol request/response behave differently then the out of band one>

2) In section 6.3 the inserted sentence has "when both are supported".  but then says that a consumer must support both.  So why this extra language?

Rich Thompson wrote:

Here is the write-up requested as a result of today's discussion of the points Mike raised on an email thread. It should also be noted that this applies to public review comments #8 & #21.


Next change

6.1.10 ClientData Type
The ClientData structure contains information the client supplied to Consumer about itself, including user-agent identification and capabilities.

 [O] string userAgent
 [O] CCPPHeaders ccppHeaders
 [O] string requestVerb
 [O] NamedString clientAttributes[]
 [O] Extension extensions[]


6.1.16 MimeResponse Type
The MimeResponse structure contains common fields relative to returning an item described by a mime type.

 [O] boolean useCachedItem
 [O] string mimeType
 [O] string itemString
 [O] base64Binary itemBinary
 [O] string locale
 [O] boolean requiresRewriting
 [O] CacheControl cacheControl
 [O] string ccppProfileWarning
 [O] NamedString clientAttributes[]
 [O] Extension extensions[]


6.3 getResource Operation
The Consumer requests a resource by invoking:

ResourceResponse = getResource (registrationContext, portletContext, runtimeContext, userContext, resourceParams );
Faults: AccessDenied, InconsistentParameters, InvalidCookie, InvalidHandle, InvalidRegistration, InvalidSession, InvalidUserCategory, MissingParameters, ModifyRegistrationRequired, OperationFailed, ResourceSuspended, UnsupportedLocale, UnsupportedMimeType, UnsupportedMode, UnsupportedWindowState

This operation's semantics are that the client/client-agent has requested additional information in a manner that utilized the Consumer as a proxy for supplying that information. As the Consumer is only being used as a proxy for accessing the resource, a number of techniques for storing the Portlet's navigationalContext are not available to it. As a result, while the Portlet's navigationalContext is supplied to this operation, neither the URL nor the response are permitted to change this navigationalContext. If a logical side effect of the invocation is changing the Portlet's navigationalContext, either the Portlet or the Producer will need to manage this change until the next opportunity to return the navigationalContext to the Consumer.
This operation can be used to fetch a resource whenever the activated URL has specified a value for the wsrp-resourceID portlet URL parameter and is the preferred mechanism whenever a value of true is specified for the wsrp-preferOperation (see [Section]. It provides all the contextual information needed for a Portlet to re-establish its state relevant to the End-User so that the generated response is able to take that state into account. The result of this operation SHOULD be identical to that achieved using the HTTP proxy method when both are supported.
Resources which are inserted into the Consmer's aggregated page MUST follow the guidelines in [Section 10.4] for the mime types described there and the relevant fragment rules, if any, for other mime types. wsrp-urlType = resource
Activation of the URL will result in the Consumer acting as a gateway to the underlying resource, possibly in a cached manner, and returning it to the user-agent. The URL for the resource (including any query string parameters) is encoded as the value of the wsrp-url parameter. When a portlet URL specifies "resource" for the wsrp-urlType portlet URL parameter, either the wsrp-resourceID portlet URL parameter or a combination of the wsrp-requiresRewrite and the wsrp-url portlet URL parameters MUST also be specified. Since the Portlet is allowed to specify either both or just one of the means of getting a resource, Consumers will need to support both the transport proxy and SOAP operation mechanisms in a manner which applies the same policy regarding the proxying of information between the client communications and Producer communications. This flexibility allows the Portlet's markup to control which resource serving mechanism is in use whenever it needs to and allows for the Portlet to provide additional guidance when both mechanisms are supported, since the fidelity of what is presented to the End-User might depend on which mechanism is selected by the Consumer.

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