[Catalyst] RFC on how to structure controllers

Wade.Stuart at fallon.com Wade.Stuart at fallon.com
Wed Jun 14 17:02:52 CEST 2006







>
> Why would you *want* to avoid sessions?
> It's much easier to manage sessions than complicated URI conventions.
>
> This blog post by Avi Bryant describes it very well imo.
>
>      http://smallthought.com/avi/?p=14
>
>      "There are 3 models:
>
>          Need quick response, but don't need back button or bookmark:
> Ajax
>          Need back button, don't need bookmark: Continuation/Callback
>          Need bookmarking or other external access: REST"
>
> > Whether you put the information in the URI into the query string
> > or into the path is not that important in terms of webarch; the
> > main advantage of using the path part is simply that it looks
> > prettier.
>
> But why would a multi page wizard or ajax requests to have
> bookmarkable URIs?
>

Agree, in fact I find many complicated apps have too many multi part
dependancies to allow bookmarking on  many pages and in those cases I
force the user to return to a safe starting spot based on session
data and uri.  I mean does it ever make sense to blindly allow users
to jump into a random spot of a 3 or 4 page billing/order "wizard"?
On the same hand you would probably want to allow a user to
bookmark a search or list view.

It really requires an inventory of every page/area of a site to
determine which areas should be directly bookmarkable,
indirectly (forward  to a sane starting point) or not allowed at all.





More information about the Catalyst mailing list