Re: can GET do for QUERY? extending Partial Content

If "global" scope on servers (or the web, depending on the server) is OK, would defining a well-known URI path be useful here?  E.g., "GET /.wellknown/search?q=string"?

> On Apr 29, 2015, at 10:12 AM, Zhong Yu <> wrote:
> On Wed, Apr 29, 2015 at 11:53 AM,
> <> wrote:
>> But hey if you and everybody else here thinks that deployment is the only
>> issue left here, then that would be good to know. :-)
> It appears to me that the only problem SEARCH solves(or rather,
> avoids) is the limitation of URI length. That *is* a deployment issue.
> So GET is fine, it's just constrained by the current deployments for
> your use cases. You want a workaround, which, nevertheless, works
> through *the current deployment*.
> Zhong Yu

Michael Sweet, Senior Printing System Engineer, PWG Chair

Received on Wednesday, 29 April 2015 19:52:44 UTC