Advantages of RESTful URI's

Ye' old general discussion board. Basically, for everything that isn't covered elsewhere. Come here to shoot the breeze, shoot your mouth off, or whatever suits your fancy.
This forum is not for asking programming related questions.

Moderator: General Moderators

User avatar
Christopher
Site Administrator
Posts: 13596
Joined: Wed Aug 25, 2004 7:54 pm
Location: New York, NY, US

Re: Advantages of RESTful URI's

Post by Christopher »

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)
User avatar
Eran
DevNet Master
Posts: 3549
Joined: Fri Jan 18, 2008 12:36 am
Location: Israel, ME

Re: Advantages of RESTful URI's

Post by Eran »

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.
Yes, I assumed that as well. It seems its not that standard though.
"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,
Could you elaborate about that something different, cause in the context of forms, form validation errors are what comes to mind...
josh
DevNet Master
Posts: 4872
Joined: Wed Feb 11, 2004 3:23 pm
Location: Palm beach, Florida

Re: Advantages of RESTful URI's

Post by josh »

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.
User avatar
Eran
DevNet Master
Posts: 3549
Joined: Fri Jan 18, 2008 12:36 am
Location: Israel, ME

Re: Advantages of RESTful URI's

Post by Eran »

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...
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.
josh
DevNet Master
Posts: 4872
Joined: Wed Feb 11, 2004 3:23 pm
Location: Palm beach, Florida

Re: Advantages of RESTful URI's

Post by josh »

I think it would be better to ask for examples of use cases in the zf tracker
Post Reply