It’s thankfully just Perl-only, and mostly a sane interface to do database queries. It could happen that not just the web front-end will use the functions in it, but other, related applications as well — though right now, it’s a web-only thing. Speaks both JSON and XML (oh the pain, that…), the front end is mostly RESTful and clean, and the reason we haven’t jumped the PSGI boat yet is simply the lack of familiarity with the new stuff + lack of time. I do have it in my mind to make a fork of it and do it the Plack way (or maybe even use Dancer to give me the routing-fu), but for the amount of (internal) traffic this is going to receive, our usual Apache + FCGI combo is more than enough.

Yeah, legacy stuff. Hard to switch from things you already have configured way better than you’d do with something new in the next half year…

So back to AcmeAPI.pm. I had had a rather short time frame to work on it, and when I’m in such a situation, I tend to keep things in as few files as possible. Wrote extensive tests to make sure things happen the way they are supposed to happen, but kept the file organisation issue to a minimum. So it’s one monolith (and another thing that does (de)serialisation for XML and JSON — to/from the same structure the API functions expect it.

RPC::Any that you mentioned in the other post — nice catch, it is an RPC, more than an API. Weird naming.

So as the pm itself is not legacy (just some of the technologies involved are), and it’s only yet used by the frontend CGI, I can freely do anything to the backend, as long as I keep the frontend’s interface and the functionality (same URL with same data doing the same things) the same.

Also, we do use VCS, we have switched to Mercurial from SVN a good while ago and we definitely use it all the time. No worries there.

In reply to Re^2: Package/module organisation question by Ralesk
in thread Package/module organisation question by Ralesk

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.