* Terrence Brannon <[EMAIL PROTECTED]> [2005-09-05 13:15]:
> You are using a REST-inspired approach to web design, not pure
> REST:
Yes. I never claimed otherwise; part of the reason for this is
that I’m writing plain old user-operated web apps, not (yet)
machine-operated XML-based web services.
* Terrence Brannon <[EMAIL PROTECTED]> [2005-09-05 13:05]:
> This is what Paul Prescod lists as Common Design Mistake #3
> when building a REST website:
I don’t expect clients to construct these URLs manually. Of
course they get there by following links from elsewhere on the
interface. The idea is
* Terrence Brannon <[EMAIL PROTECTED]> [2005-09-05 13:30]:
> What if you had to visit aristotle.perlmonks.org instead of
> simply visiting perlmonks.org and having it authenticate you
> based on a cookie?
You are forgetting HTTP authentication. You’d visit (in common
URI syntax) http://user:[EMAI
"A. Pagaltzis" <[EMAIL PROTECTED]> writes:
> * Terrence Brannon <[EMAIL PROTECTED]> [2005-09-04 03:15]:
>> To me, that means "no cookies". But your discussion of 401 and
>> 403 would imply such a mechanism for recognizing who made the
>> request?
>
> I do (still?) use cookies.
I think it is pragm
"A. Pagaltzis" <[EMAIL PROTECTED]> writes:
> * Terrence Brannon <[EMAIL PROTECTED]> [2005-09-04 03:15]:
>> To me, that means "no cookies". But your discussion of 401 and
>> 403 would imply such a mechanism for recognizing who made the
>> request?
>
> I do (still?) use cookies.
You are using a RES
"A. Pagaltzis" <[EMAIL PROTECTED]> writes:
> * Terrence Brannon <[EMAIL PROTECTED]> [2005-09-03 19:15]:
>> A user requests *operations* - login, add user, view user which
>> are materialized by model actions and feedback on success
>> failure via the view/page.
>
> I model my applications as a se
