Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Hi

    Quite possibly not.

    I did say I was trying to clarify my ideas.

    And, like all learners (yes, even you), I have to go thru a learning phase.

    Life, Perl and REST are all topics to be learned.

    Fundamentally, that means I do not possess absolute or infinite knowledge, and never will.

    If I get things wrong, it doesn't matter. What matters is whether or not I get feedback in a form which helps me correct my misunderstandings.

    And if I keep my misunderstandings to myself, they'll never be corrected. So - what can I do

    • Not claiming to be that knowledgeable, but what made me "understand" REST was the book "RESTful Web Services" []. That in turn cites the original thesis on REST []. Some ideas that I took away were:

      • keep a uniform interface, which is what the HTTP methods already give you;
      • give every "resource" in your application a(t least one) URL;
      • avoid keeping application state on the server, for scalability;
      • hyperlinks send the application from state to state on the client side, in other words the current state's "representation" has links from the current state to whatever next states there are in the application (or to other applications, e.g. externally-linking URLs)

      The last one is "REpresentational State Transfer".