You can certainly affect caching policies in GET responses:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html
I'd still say GETting a list of images using POST is where the design is
smelling, don't blame the JSR this particular use case is cumbersome.
On Wed, Dec 31, 2008 at 4:34 PM, Gili <cowwoc_at_bbs.darktech.org> wrote:
>
>
> Daniel Larsson wrote:
> >
> > On Wed, Dec 31, 2008 at 4:50 AM, Gili <cowwoc_at_bbs.darktech.org> wrote:
> >
> >> POST /images: creates a new image
> >> POST /images?order=random: returns images in random order
> >
> >
> > Why are you POSTing to GET a set of images?
> >
>
> Explained here:
> http://n2.nabble.com/JSR311-encourages-bad-design-tp2094913p2096335.html
>
> Gili
> --
> View this message in context:
> http://n2.nabble.com/JSR311-encourages-bad-design-tp2094913p2096338.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>