<br><br><div><span class="gmail_quote">On 5/3/06, <b class="gmail_sendername">Manlio Perillo</b> <<a href="mailto:manlio_perillo@libero.it">manlio_perillo@libero.it</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Nicola Larosa ha scritto:<br>>> Stateless protocols like HTTP use sessions for client authentication.<br>><br>> Don't say such a thing in REST company, you could be lynched. ;-)</blockquote><div><br><br>no the correct statement is
<br><br>Stateless protocols like HTTP use sessions to STORE STATE.<br><br>Nicola is correct, HTTP only support authentication on every request since it is STATELESS and only supports BASIC and DIGEST.<br><br><br>if you want to make it STATEFUL then using "sessions" is just one of many ways to store and track that STATE.
<br>if you want to store authentication tokens as part of that STATE you can, but that has NOTHING to do with HTTP Authentication and is probably NOT secure, but it has NOTHING to do with <br>"... HTTP using sessions for client authentication."
<br><br><br><br></div></div>