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#161] tri-state usesMethodGet

Title: Message
Actually, the flag defined by Eilon was implied by my proposal. The third value (I support it only if the Consumer supports it) means that Consumers must send information about their support of method=get.
-----Original Message-----
From: Eilon Reshef [mailto:eilon.reshef@webcollage.com]
Sent: Mon, December 02, 2002 08:07
To: 'Gil Tayar'; wsrp-wsia@lists.oasis-open.org
Subject: RE: [wsrp-wsia] [I#161] tri-state usesMethodGet

This can be a flag passed by the Consumer saying whether it supports form method=get. (Namely, it doesn't use URL parameters).
The way the flag is defined today is almost useless: if the Producer uses form get, then the Consumer has nothing to do about it.
Gil's suggestion, or the variation I proposed above, at least allows a smart producer to do something about a non-supporting consumer (namely, to use only method=post).
-----Original Message-----
From: Gil Tayar [mailto:Gil.Tayar@webcollage.com]
Sent: Sunday, December 01, 2002 6:13 AM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [I#161] tri-state usesMethodGet

Issue: 161
Status: Active
Topic: interface
Class: Technical
Raised by: Gil Tayar
Title: tri-state usesMethodGet
Date Added: 1-Dec-2002
Document Section:   v0.85/7.1.2
usesMethodGet today means - I have it or I don't. I would like to add a new one, which says I'll use methodGet only if the Consumer supports it, otherwise I'll fall back on other methods. This enables the Producer to support all Consumers.
Gil Tayar

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

Powered by eList eXpress LLC