Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apache XMLRPC 1.0 Released

Posted by Hemos on from the new-code-released dept.

jvanzyl writes "The Apache XMLRPC team is pleased to announce the 1.0 release! Apache XML-RPC is a Java implementation of XML-RPC, a popular protocol that uses XML over HTTP to implement remote procedure calls. Apache XML-RPC was previously known as Helma XML-RPC. If you have code using the Helma library, all you should have to do is change the import statements in your code from helma.xmlrpc.* to org.apache.xmlrpc.*."

12 of 28 comments (clear)

  1. Re:Now... by danielrall · · Score: 2, Informative

    Or perhaps you don't have a clue what XML-RPC is? Try the spec for clarification.

    --
    Daniel Rall
  2. Soap by Karma+50 · · Score: 3, Interesting


    Is this compatible with SOAP? I thought they were working towards that but there's nothing in the announcement about it ...

    --
    http://www.thehungersite.com
    1. Re:Soap by Oily+Tuna · · Score: 3, Informative

      Were you thinking of Axis?. It's still work in progress, because SOAP is too

      --
      Mmmmmmm ... sushi.
  3. Re:Now... by sjehay · · Score: 2, Informative

    I think you've made a mistake here and haven't quite understood what XML-RPC is for... it's not designed and can't be used for general bells-and-whistles on websites, but instead in its simplest form is a way for two applications to communicate with each other by invoking remote methods, passing parameters, getting results back etc, as any RPC protocol is. It shouldn't affect web design at all...

  4. Re:Whats the deal by thedarkstorm · · Score: 2, Informative

    I don't think you truly see the potential here. This would allow you to do language independant and platform independant (exclude OS's that don't support TCP/IP) methodology of doing RPC. Suppose for example you have a VB server (cough cough) application on Windows and a Kylix app on Linux and you need to perform RPC. This would be a VERY simple way of doing it without the bloat of SOAP.

    --
    ... hey ... I had a .sig, bu then MicroSo$$ embraced it...
  5. interesting by thedarkstorm · · Score: 2, Interesting

    I've been following this for some time since I accidentaly bought the O'Reilly book by mistake (was actually looking for a book on SOAP) when it was onsale. The 'pusher' behind this is MicroSoft. What's interesting is the big pusher that used to be behind SOAP was MicroSoft as well. Correct me if I'm wrong, but XML-RPC is a much ligher-weight XML competitor to SOAP-RPC. Yes, SOAP does much more than RPC, but that was the original intention behind it. Could MS be pushing XML-RPC because it's lost the majority of control of SOAP??

    --
    ... hey ... I had a .sig, bu then MicroSo$$ embraced it...
    1. Re:interesting by mikemcc · · Score: 3, Informative

      Microsoft was not a driving force behind XML-RPC. That credit goes to Dave Winer of Userland Software. http://www.xmlrpc.org/spec

      XMP-RPC predates SOAP, and in fact was a major inspiration for SOAP. If you look at the specification for the latter protocol, http://www.w3.org/TR/SOAP/ , you will see that Dave Winer is one of the eight authors credited.

      I have not seen anything which indicates that MS "lost control" of SOAP. MS engineers are 4/8 of the credited authors behind the SOAP 1.1 protocol, and MS's entire "Web Services" initiative depends heavily on SOAP.

    2. Re:interesting by Schwarzchild · · Score: 2
      Correct me if I'm wrong, but XML-RPC is a much ligher-weight XML competitor to SOAP-RPC.

      Correct. XML-RPC only implements simple containers for vars while SOAP presumably allows data structures like arrays, lists, etc.

      IIRC SOAP was created by Dave Winer and Microsoft because there was some need for passing more than a simple but Winer still pushes both protocols even though it seems like he prefers XML-RPC.

      --

      "sweet dreams are made of this..."

  6. Wot's Uh... The Deal by ffatTony · · Score: 2

    I agree with what you're saying, but what about corba? I realize it is harder, but it seems like a more performance friendly solution, although I admit XML-RPC is more elegant. Perhaps the next corba spec will use xml for communication, although I truly hope not, unless some sort of compression/decompression is performed to reduced transit times.

    1. Re:Wot's Uh... The Deal by the+eric+conspiracy · · Score: 2

      Corba is a fscking b*tch to implement. XML-RPC is far more elegant and thus we have many more implementations (usually free) to choose from.

  7. "Interceptors" by Hard_Code · · Score: 2

    I wrote a patch which adds "interceptors" ("filters", whatever) to the library, which allow manipulation of the data stream and arguments.

    http://aeolus.cit.cornell.edu/xmlrpc.html

    I posted this to both lists, and so far nothing as far as responses.

    --

    It's 10 PM. Do you know if you're un-American?
  8. Re:Whats the deal by the+eric+conspiracy · · Score: 2

    Yeah, I just finished doing something like this. I needed an way of managing accounts to an IMAP mail server from a Java based web site - on the mail server I wanted to use a Perl IMAP module. XML-RPC to the rescue. A Java client and a Perl server - done.