Re: the meaning of stateless

Will Hartung <[email protected]>
Newsgroups gmane.comp.web.services.rest
Message-ID <CAA2iDiArXBwx02e1uCtgdD6XJTXk=Rm5-g19vN75mxChLx0FLg@mail.gmail.com>
From a REST perspective, HTTPS is absolutely stateless, because it is
orthogonal to the application state. TCP itself is a stateful protocol. We
just don't see it at the application level. The application is ignorant
that I've dialed the modem, had it connect it's carrier waves and that it's
handshake and compression are working before I tunneled PPP over it in
order to stand HTTPS on top of that.

All of those are stateful in their own right, but have no effect on the
application.

These are separate issues.



On Mon, Apr 22, 2013 at 10:13 AM, Brian Craft <[email protected]> wrote:

> **
>
>
>
>
>
> On Mon, Apr 22, 2013 at 3:09 AM, Matt McClure <[email protected]>wrote:
>
>> On Apr 21, 2013, at 7:52 PM, Brian Craft <[email protected]> wrote:
>>
>>
>>
>> Fielding's definition didn't do much for me, because the terms aren't
>> adequately defined, and there aren't enough examples to clarify his intent.
>> Also, some of the claims seem to be at odds with practice. Again, the "POST
>> to query" thing involves storing state between requests, while Fielding
>> says RESTful APIs are better because of "not having to store state between
>> requests". Well, which is it?
>>
>>
>> I think a key distinction is creating and destroying resources vs. other
>> kinds of state. The former is a key feature of REST.
>>
>>
> That's very much the impression I'm getting: that it's not generically
> server-side state that is the key issue. It's something to do with the
> difference between explicitly created state that can be directly referenced
> with a URL vs. implicit state. If that is what it's about, then "stateless"
> should be qualified, and some of the claims should be relaxed.
>
>  
>

-- 
CONFIDENTIALITY NOTICE: The information contained in this electronic 
transmission may be confidential. If you are not an intended recipient, be 
aware that any disclosure, copying, distribution or use of the information 
contained in this transmission is prohibited and may be unlawful. If you 
have received this transmission in error, please notify us by email reply 
and then erase it from your computer system.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.