I use CGI::Application::Dispatch quite heavily, and my workflow generally includes fleshing out the request handling and responses using something like the Chrome's REST Console.

Once I have that fleshed out, I like to us YUI 3 (specifically Y.IO) to build out one of many possible client interfaces.

The important message here is the workflow. The tools mentioned are what I use, but you can use anything. It's best to work out the REST API first, without the UI being built up along side. Once you get the API and build up your first (of many) REST consuming clients, then you might have to slightly adjust your API if done right, but you don't want to be molding your hopefully long lived REST API with what will be a relatively much shorter lived client.


In reply to Re: Firefox/Javascript/Perl CGI argument passing issue by perlfan
in thread Firefox/Javascript/Perl CGI argument passing issue by beckmanel

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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! —
  • 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:
    & &amp;
    < &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.