Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Stanimir Stamenkov <s7an10@netscape.net>
Newsgroups: comp.lang.java.programmer
Subject: Re: Web services/SOA - The right way
Date: Wed, 31 Aug 2016 16:23:13 +0300
Organization: A noiseless patient Spider
Lines: 35
Message-ID: <nq6lo2$6ms$1@dont-email.me>
References: <aa1331d1-623a-4d8a-9812-ceccf9f72c19@googlegroups.com> <b92073ee-24b3-4667-a938-bf5395977e7b@googlegroups.com> <npf7s1$1k5$1@gioia.aioe.org> <npiifg$1791$1@gioia.aioe.org> <npilhr$1bbs$1@gioia.aioe.org> <npk1g6$16ga$1@gioia.aioe.org> <npldph$1fkq$1@gioia.aioe.org> <npmkdf$1618$1@gioia.aioe.org> <npo211$1m4c$1@gioia.aioe.org> <npqkhc$1v9a$1@gioia.aioe.org> <npqlr8$13f$1@gioia.aioe.org> <nq08dv$e3n$1@dont-email.me> <nq59fa$1r9j$1@gioia.aioe.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 31 Aug 2016 13:23:14 -0000 (UTC)
Injection-Info: mx02.eternal-september.org; posting-host="eca23f05cb49d554ff3b985a27fc0a37"; logging-data="6876"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/jACGbUIibqxg2dN1CYQRf"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 SeaMonkey/2.45
In-Reply-To: <nq59fa$1r9j$1@gioia.aioe.org>
X-Face: "@)%Vlap6d%OVYDS}B4YUWE@yUy+^!w/+.q.,c5kjI#+uG?kYP&r/pTjNWgo:g[A,O=AL3/ j&4Le2cau$<e=FPq~GbeZ6DW1Grey[VHn8?ktzvoQtzlg;]&rh8g]CD+_BC7d[gW{Yx&_X*4Q$h&nJ l@t(|4R4:T='&]U#ui+z9OC$.~gJjU93kh:Ojc$Cz0n#I9!~!9ay?E<UlW&5,IFX1*KtA>MYEFst$y y"m]M7tq\S(>[a$x0x8%S
Cancel-Lock: sha1:wUNFyigu3Y8BfHxmknrcKEXBk5w=
Xref: csiph.com comp.lang.java.programmer:35522

Tue, 30 Aug 2016 20:47:39 -0400, Arne Vajhøj:
> On 8/28/2016 10:59 PM, Stanimir Stamenkov wrote:
>> Fri, 26 Aug 2016 20:11:21 -0400, Arne Vajhøj:
>>
>>> Fielding's original paper that defined REST section 5.1.3 state:
>>>
>>> <quote>
>>> each request from client to server must contain all of the 
>>> information
>>> necessary to understand the request, and cannot take advantage 
>>> of any
>>> stored context on the server. Session state is therefore kept 
>>> entirely
>>> on the client.
>>> </quote>
>>
>> The relevant resource content/state is certainly always available 
>> when processing a request.
>
> Completely stateless if difficult in practice.

Stateless is an illusion – the resource itself holds/represents a 
state...

> But it is still not the same as using the session object to store 
> service related data.

though the state is not user session specific, yes.

I still think people read specifications too literally, and likely 
miss the basics.

-- 
Stanimir