Next in thread →
Next in month →
Re: [wsrp-interfaces] Clarification on mimeAttributes vs clientAttributes
Hi Nate, in case of an upload we stuff in the content type header which in case of multipart could contain e.g. the boundary related to this particular upload. e.g. <p631:uploadContexts> <p631:mimeType>multipart/form-data; boundary=---------------------------7da317c2c00d4</p631:mimeType> <p631:uploadData>some CDATA here</p631:uploadData> </p631:uploadContexts> Mit freundlichen Grüßen / Kind regards Richard Jacob Team Lead Portal Standards & WCM development WSRP Standardization Lead IBM Software Group, WPLC WSS Websphere Portal Foundation Development 1 Phone: +49-7031-16-3469 IBM Deutschland Research & Development E-Mail: Schoenaicher Str. 220 71032 Boeblingen Germany IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Martin Jetter Geschäftsführung: Dirk Wittkopp Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294 From: Nathan Lipke <> To: Date: 07/19/2010 10:03 PM Subject: [wsrp-interfaces] Clarification on mimeAttributes vs clientAttributes Does anyone have a reason for having both of these? If so is there a difference? 1. http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-spec-os-01.html#_UploadContext mimeAttributes: Attributes received from the client (e.g. http headers, other attributes relative to the upload file, etc.) that are not represented elsewhere within the protocol.2. http://docs.oasis-open.org/wsrp/v2/wsrp-2.0-spec-os-01.html#_ClientData 1. clientAttributes: Attributes received from the client (e.g. HTTP headers) which are not represented elsewhere within the WSRP protocol and which the Consumer is choosing to supply to the Portlet. When this structure is being supplied to the getResource operation, Consumers SHOULD supply the same set of items which would have been supplied using the HTTP proxy method of serving the resource. Thanks, Nate
Next in thread →
Next in month →