Sergiu Dumitriu wrote: >> I don't like it since I'm not sure this is very RESTful. > > +1, but it depends. > > A resource is identified by the path, without query parameters. > Not sure about this... At the protocol level, AFAIK, query parameters are part of the URI an though they contribute to identify the resource.
So, at this level, imho, it is almost a philosophical or best practice matter. Anyway I thought again about query parameters and actually the main reason why they are problematic is because apparently many caching agents, by default, don't take into account query parameters. Squid, for example, does so (but it can cache resources by using the full URI http://foo/bar?param=value if configured properly). So if we want to be sure that caching occurs, maybe it's best to identify cacheable resources without using query parameters. -Fabio _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
