Re: the meaning of stateless

On 21 Apr 2013 18:12, "Brian Craft" <[email protected]> wrote:
>
>
>
> Storing session information isn't negotiable, and is orthogonal to API
design. For example, no one sits down to design an API and says "Oh, a
restful API is stateless, so I can't use HTTPS, because it stores session
state on the server." The API design occurs independent of the statefulness
of the communication, which is dictated  by security concerns.

Actually I know people do actually do this.

Making resources in your app that are publicly accessible non-https means
that the cacheability of those resources is significantly increased
precisely because the stateless constraint is being conformed with and
therefore shared network intermediaries (I.e. caches) can transparently act
on behalf of the server.

Afaict, that is a valid design choice.

Cheers,
M