No. It's just more RESTful. I mainly build API with Dancer, so I tend to follow a RESTful design. http://en.wikipedia.org/wiki/Representational_state_transfer GET is used to list/query a collection and also retreive an object POST is used to create an object into a collection. PUT to update an object DELETE to delete an object Since you are quering a collection, I'd suggest using GET. On Thu, Oct 16, 2014 at 3:23 PM, John Stoffel <john@stoffel.org> wrote:
Jacques> Here is how I do it. Check the gist for better formatting. Jacques> https://gist.github.com/jacqueslareau/1e9dcc04d416e1216161
Jacques> status_ok is because it's an API. You can use the value returned in a template instead.
Thanks a ton for this pointer, I'll look into it more deeply.
Now for a stupid question, has everyone moved away from using 'post' to instead using 'get' as the method of choice for form handling in general? I'm still stuck in the old PHP days honestly, but trying to move upto newer stuff. Tried Rails years ago, but all the examples of building a blog weren't what I needed/wanted. Sigh... I don't know why everyone things a blog is a good example.
Anyway... sorry for whining. I'll take a look at your code and see how I can make it work for me.
John _______________________________________________ dancer-users mailing list dancer-users@dancer.pm http://lists.preshweb.co.uk/mailman/listinfo/dancer-users