Re: How to differentiate between multiple Operations which use the same HTTP Action

Hi,

think about the following use-case:
You have a collection and you have the implicit GET based operation to 
retrieve the
the collection itself (the one we are discussing in parallel is not 
required to have a named operation for, Issue #11).
Now you want to offer a second operation which allows querying the 
collection
with some complex syntax that you don't want to serialize in the query 
string (maybe it is
too complex to be expressed as URI template). Therefore you define the
operation such that it expects a query object:

...
operation: [
{
     @type: "http://example.org/QueryOperation",
     method: "GET",
     expects: "http://example.org/classes/Query"
}

So on the server side you are forced to distinguish two GET based requests.
The only way is to consider the request body.

Greets

On 04/23/2014 03:19 PM, Markus Lanthaler wrote:
> Hi Thomas,
>
> On Tuesday, April 15, 2014 4:25 PM, Thomas Hoppe wrote:
>> I currently try to model a resource which would support more than one
>> operation based on HTTP GET.
> Really? What are you trying to do?
>
>
> --
> Markus Lanthaler
> @markuslanthaler
>
>
>
>
>