Advantages of RESTful URI's
Moderator: General Moderators
- Christopher
- Site Administrator
- Posts: 13596
- Joined: Wed Aug 25, 2004 7:54 pm
- Location: New York, NY, US
Re: Advantages of RESTful URI's
No, just two actions -- the first is to accept requests until the form validates; the second is wherever the redirect goes (which does not have to be a literal "success" page).
(#10850)
Re: Advantages of RESTful URI's
Yes, I assumed that as well. It seems its not that standard though.I am a little confused from reading this who does what. I assumed that the usual practice was that a form action submits to itself until all fields are valid data.
Could you elaborate about that something different, cause in the context of forms, form validation errors are what comes to mind..."We're talking about form validation errors" - ( both of us? cuz like I said I was under the presumption we were talking about something different,
Re: Advantages of RESTful URI's
Well for instance consider the fact not all applications are C.R.U.D.
You might want a flash messenger telling them they have 5 new responses to questions they posted
you might want it to tell them about new private messages
might want to tell them their account is inactive, etc...
for this different namespaces would be useful, so users can opt-in to the different notification types, which you might choose to implement via the flash messenger.
Of course it could also be used to separate success / error messages when used on a CRUD screen as well. Ex. if your client asks you to globally remove all the delete messages, but they are scattered everywhere but only displayed in one place, it would be useful just to go where they are being displayed and filter out by message type, rather then remove all the hard-coded messages at risk of having to go put them back in later.
You might want a flash messenger telling them they have 5 new responses to questions they posted
you might want it to tell them about new private messages
might want to tell them their account is inactive, etc...
for this different namespaces would be useful, so users can opt-in to the different notification types, which you might choose to implement via the flash messenger.
Of course it could also be used to separate success / error messages when used on a CRUD screen as well. Ex. if your client asks you to globally remove all the delete messages, but they are scattered everywhere but only displayed in one place, it would be useful just to go where they are being displayed and filter out by message type, rather then remove all the hard-coded messages at risk of having to go put them back in later.
Re: Advantages of RESTful URI's
What does this has to do with form submission? those are separate checks that occur in a user's dashboard, header and so forth. How is this related to POST requests? the only thing relevant here might be the account deactivation. It could be a login error message, but I don't see why it would need a redirect + sessions to show it.You might want a flash messenger telling them they have 5 new responses to questions they posted
you might want it to tell them about new private messages
might want to tell them their account is inactive, etc...
Re: Advantages of RESTful URI's
I think it would be better to ask for examples of use cases in the zf tracker