Personally, I find the approach of thinking of communication as RPC problematic. I think it can lead to APIs that set up data piecemeal instead of atomic calls that update an entry.

For example, your CMS might have methods like ->set_title and ->set_body for an item. I think it would be quite bad to expose these procedures to the outside world. The API should be /item/create and /item/update, both of which supply the complete information to create or update the item. That way, you prevent confusion if only one of the calls succeeds and the other fails.

In reply to Re^2: Perl, Android web app, AJAX, JSON by Corion
in thread Perl, Android web app, AJAX, JSON by monx663

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.