I am the author of a scaffolding for Catalyst (Catalyst::Example::InstantCRUD). The purpose of it is two-fold - first you can treat it like you treat h2xs or ExtUtils::ModuleMaker - something that generates a template. Second it is meant as a learning tool - it generates a working application so one can check how it works and try to customize it. Currently it uses a traditional URI schema: /name/view/id, /name/edit/id etc. I am thinking about adding a REST functionality to it - but this would mean quite a bit of changes:

• Changing the URI schema to less intuitive:

     # POST         /foo                -> create new record
     # GET          /foo                -> list all records
     # PUT          /foo/by_id/<pk>           -> update record
     # DELETE       /foo/by_id/<pk>           -> delete record
     # GET          /foo/by_id/<pk>           -> view record
     # GET          /foo/by_id/<pk>/edit_form -> edit record form
     # GET          /foo/create_form    -> create record form
  [download]

  or similar.
• But perhaps more important it would also mean using the machinery for serializing the content based on the HTTP Requests content-type header (see Catalyst::Controller::REST).
• And finnaly it needs additional dispatching mechanism - so that the queries are routed to methods called foo_PUT or foo_DELETE (see as above).

So it introduces a lot of complications - that would be an additiona obstacle for those that don't want to go the full REST path, both the learners and those who just use it as a template generator. Among the other frameworks I see that Django uses the traditional URI structure - and I think Rails uses REST.

Do you thing REST is worth those complications? Or maybe I should generate two applications: one RESTful and another one more traditional (in two additional subdirs)? Or maybe you have some other ideas?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.