http://www.symfony-project.org/book/1_0/06-Inside-the-Controller-Layer

The strength of the documentation is one of the main reasons I chose to go with symfony as my PHP web framework of choice.

After all, we’d have access to all those databases, so why not use them?

Or maybe using an API would just make things more consistent with non-drupal apps which can’t rely on the direct db access.

Funny how my thoughts often turn out to be about two weeks _behind_ yours. Methingks the whiteboard I drew today is more-or-less what you’ve written here!

Nice 1.

please explain more about your post

thank you in advance

aditya

However I think all this does mean that you’ve got to know something about how the routing rules were constructed to be able to use link_to. ie. it doesn’t seem like you can do something like link_to(’mylink’, ‘/1/nodetail/category’)

I suppose this is a somewhat contrived example anyway, because using /nodetail/category in the url isn’t needed - these values default to detail=false and category=true anyway. I just used the example to show how you can allow a url which looks quite different from the underlying request parameters.

Great post, however I’m still confused about something. You provide the example of:

url: /:id/nodetail/category
param: { module: mymodule, action: myaction, detail: false, category: true, year: 2008 }

as your routing rule, however I don’t see how you can generate that pattern using an internal symfony URL helper like url_for() or link_to(). From what I understand these helpers only accept URIs in the format of ‘module/action’, is there a way around that?