Stories
Slash Boxes
Comments
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.

I won't bite... hard 6 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • sorta (Score:1)

    by pudge (1) on 2002.01.16 17:35 (#3278) Homepage Journal
    I am thinking of and mapping out a web services API for Slash / use Perl, starting with journals, to allow you to read/post entries. No specific plans or ETA yet.
    • Please.... no SOAP/XMLRPC...

      How about GET /~matts/journal with Accept: text/xml, and it returns an XML representation. And POST to /~matts/journal will put a new journal entry up, accepting both HTML and XML (and maybe even POD!) in the Content-Type field.

      HTTP fucking rocks, I wish people would stop using SOAP and XMLRPC when it's just plain not needed (not implying that's your intention, pudge, just most people see web services == SOAP). Of course I have a talk about that :-)
      • HTTP fucking rocks, I wish people would stop using SOAP and XMLRPC when it's just plain not needed

        SOAP and XML-RPC *are* HTTP. :p

        I agree with your sentiment (when people started talking about this "new" thing called web services, I had similarly virulent reactions), but the key here is interoperability. More people can play this way. Further, this isn't just for use Perl, it is for Slash. I likely will use SOAP or XML-RPC or both, because I see no reason at all not too, and because it gives me the

        • Well I could point you at my slides, but the most important points are:

          1. If you can do SOAP over HTTP you can do plain HTTP. It's not that hard, in fact I submit it's easier for the majority of languages (perhaps Perl excepted [soaplite.com]).

          2. SOAP provides you with zero logging unless you do it yourself. Whereas with straight HTTP the server logs for you. If you use SOAP at http://use.perl.org/soap, then you might log 2000 calls to that URI a day, but you have no idea how they break down. That's bad, m'kay?

          3. No
          • 1. Yes, I didn't say it was hard. However, I wouldn't say it is easier. Construct a POST request and handle authentication and send it, or call a method? While for *me* it is easier to do a simple HTTP request with all that, for most people it is not. Plus, there are already many tools and APIs [blogger.com] out there for dealing with journals via XML-RPC/SOAP web services. For this growing group, hooking into Slash journals would be entirely trivial, if the APIs were compatible.

            2. Slash already handles its own lo
    • In the meantime, I've written WWW::UsePerl::Journal. Grab it from CPAN. Read only at the moment though...
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.