Topic: REST and smarter user interfaces
All the recent buzz about REST is causing me to re-examine it. I've been rather anti-REST in the past because it seems like it tends to promote very fine grained user-interfaces, where I tend to need to use more powerful UIs.
For instance, lets say you are making a reservation system for a vacation service. You're likely to have to collect information on the people attending, if they want their meals included in the package, or if they want more flexibility to eat on their own. You'll need to collect information on all the little side "excursions" or various other extra cost items.
Now you could have a ton of page views for all of this and make it RESTful, but that would be rather un-friendly. You could have a plethora of forms on each page (so that each form is still interacting the the appropriate REST controller), but that's still a little unfriendly -- if people fill out the whole page and don't realize that you have to submit each item separately, etc
If you have a single more sophisticated form, the action handling it is going to have to break apart the request and chain it through many other controllers:action pairs, which seems workable on the surface, but it doesn't look like actions are designed to really chain that way.
Of course its highly likely that even with the more involved form there might be a need for the more simple REST controllers/views for tweaking things after the initial (wizard-like) creation.
Has anyone else starting exploring how REST and UI interact and can offer some advice?