Re: [rest-discuss] GET Request length limitation.
- Mark Baker wrote:
> On Fri, Oct 08, 2004 at 08:36:51PM -0400, Joe Gregorio wrote:I'm confused now. What can I expect after I've POSTed something to a
>>I'm not quite sure I understand the problem, are you saying
>>that there is an implicit expectation of the client
>>that POSTing will always return the results of the
>>query instead of just a Location: header of where
>>to get the results henceforth?
> Sorry Joe, I thought this was the query-document-in/results-document-out
> idiom, not the separate resource being created. But no, I have the same
> issue with either, a) expecting the query results in the POST response,
> and b) expecting the query results in a GET on the returned Location
> URI. The issue is not the mechanism, it's the additional expectation,
> since it's not one that can be met by other resources and therefore
> neither uniform nor RESTful. Said another way, I couldn't POST a query
> document to any old resource and expect it to understand that I expect
> back the results, nor could I assume that anything I got back from an
> arbitrary resource was the results of the query document being processed
> as a query.
- On Wed, 2004-10-27 at 05:32, S. Mike Dierken wrote:
> > > operation. You don't need to 'send a query' - what you typically want toPing. The light went on.
> > > is to 'retrieve results'.
> > Tell me that's not nit-picking please?
> It's not nit-picking.
> > why differentiate?
> Because a 'query' is not /required/ to be different than a retrieval. There
> is no uniqueness to it. It also shifts focus from
> functions/methods/operations to the actual data/information being exchanged.
> Creating uniformity between the two actions allows your systems to work with
> other people's software even if those other people don't know what your
> particular 'query' is supposed to mean. For example, how soon would
> AltaVista or Google assign a developer to build code to support "Dave's
Thanks for that.
> > Go to the shop vs get a newspaper?'Don't care how. Its the newpaper I want.' Yes.
> > Same thing?
> No, the difference is that "go to the shop" is the detailed implementation
> approach, whereas "get a newspaper" is the result regardless of the
> > Good. I'd hate to ask all systems to host server software!<grin/> OK, dream on.
> Oh, but imagine what could be possible if they did!
The server in my fridge is too much for me :-)