On Tue, Sep 17, 2013 at 12:27 PM, Gabriel Wicke <[email protected]> wrote: > > An end point that wants to be cacheable should only use one query > parameter, which might well be a path. Hypothetical examples: > > http://wiki.org/wiki/Foo?r=latest/html > http://wiki.org/wiki/Foo?r=123456/wikitext
So now you're cramming multiple parameters, ordered, into one parameter? Why not go all the way and do http://wiki.org/wiki/123456/wikitext/Foo then? But IMO, that's ridiculous. > An alternative solution would be to specify a list of required query > parameters and a canonical ordering, and to reject (or redirect) > requests not conforming to this spec. "reject" is even more ridiculous. "redirect" is less ridiculous, but is strange and will increase latency and number-of-requests for clients that don't know the magic order. What is the actual benefit we're trying to get here? All I've gotten so far along those lines is "improve cacheability", but it doesn't seem to have been established whether caching even needs improving in this area. -- Brad Jorsch (Anomie) Software Engineer Wikimedia Foundation _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
