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


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

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

Subject: Re: [wsrp-wsia] [I#187] How does POST data reach the Producer

I second that.
Moreover the request parameters will normally already be parsed when the
consumer portal receives the request. So it is much simpler and efficient
to pass them along with the WSRP SOAP requets. Of course in such a case we
would need to distinguish between parameters and upload data.

Best regards
Carsten Leue

Dr. Carsten Leue
Dept.8288, IBM Laboratory B÷blingen , Germany
Tel.: +49-7031-16-4603, Fax: +49-7031-16-4401

             Subbu Allamaraju                                              
             12/17/2002 03:16          wsrp-wsia@lists.oasis-open.org      
             PM                                                         cc 
                                       Re: [wsrp-wsia] [I#187] How does    
                                       POST data reach the Producer        

I believe Andre's use case is a common one, and I don't think consumers
can always send the of the body of the request data as is without ever
parsing it. Why force consumers to always recreate the body?



Andre Kramer wrote:
> If the consumer has already done the work of breaking up the POST data
> why require that the protocol forwards it as a single entity to the
> producer? The scheme I submitted would (optionally) allow a processed
> POST to be forwarded as string/value and mime parts to a producer (who
> can always convert it to a single multi-part mime if it requires
> a single binary input.
> An example use case for the consumer processing POST data would be a
> consumer portal that keeps an audit trail of user submissions.
> regards,
> Andre
>     -----Original Message-----
>     *From:* Eilon Reshef [mailto:eilon.reshef@webcollage.com]
>     *Sent:* 16 December 2002 00:27
>     *To:* wsrp-wsia@lists.oasis-open.org
>     *Subject:* RE: [wsrp-wsia] [I#187] How does POST data reach the
>     A concrete suggestion follows:
>     The rationale is that POST data should be opaque to the Consumer.
>     Hence, I suggest that we do not require the Consumer to parse the
>     POST data in any way. Instead, the Consumer should pass an argument
>     to the performInteraction operation (and not to the getMarkup). The
>     argument may be called payload. This argument will contain the body
>     of the HTTP request that comes from the browser as-is, excluding the
>     HTTP headers - this should take care of all form POST scenarios,
>     including document upload and general parameters.
>     With this thread of thought, requestParameters are not needed for
>     form POST. They may or may not be needed for form GET (which is a
>     separate issue).
>     Eilon
>         -----Original Message-----
>         *From:* Gil Tayar [mailto:Gil.Tayar@webcollage.com]
>         *Sent:* Sunday, December 15, 2002 1:49 AM
>         *To:* wsrp-wsia@lists.oasis-open.org
>         *Subject:* [wsrp-wsia] [I#187] How does POST data reach the
>         Issue: 187
>         Status: Active
>         Topic: interface
>         Class: Technical
>         Raised by: Gil Tayar
>         Title: How does POST data reach the Producer
>         Date Added: 15-Dec-2002
>         Document Section:   v0.85
>         Description:
>         This is not made clear. Two suggestions I heard - uploadData and
>         requestParameters. Both have their problems. Maybe something
>         more explicit?
>         Resolution:

To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

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

Powered by eList eXpress LLC