Slashdot Mirror


Apache XMLRPC 1.0 Released

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.*."

5 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. 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. 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.