hi roy,
but how i see the current design of (micro)sling - there is not any
intention of 'storing' actions in the uri. of course a user can still
code some 'actions' in his script - but this would not be the fault of
sling. the 'selectors' are primarily used to resolve to a different
'view'
Hi Roy,
Thanks for the clarification and links - comments inline.
On 10/15/07, Roy T. Fielding [EMAIL PROTECTED] wrote:
...The original Web design notes forbid the use of GET for any action
that is considered to have side-effects, because such an
implementation allows users to be tricked into
I seem to have failed to get my point across when I last visited
Basel and we talked about what can and cannot be done in a selector.
The original Web design notes forbid the use of GET for any action
that is considered to have side-effects, because such an
implementation allows users to be
thanks for this clarification.
but how i see the current design of (micro)sling - there is not any
intention of 'storing' actions in the uri. of course a user can still
code some 'actions' in his script - but this would not be the fault of
sling. the 'selectors' are primarily used to resolve to a
