Archive of UserLand's first discussion group, started October 5, 1998.

Re: Working XML-RPC servers

Author:James Carlyle
Posted:6/24/1999; 6:24:07 AM
Topic:Working XML-RPC servers
Msg #:7771 (In response to 7739)
Prev/Next:7770 / 7772

I am attempting to describe the application that a RPC server provides using the following RDF format (sample from Mail to the Future). The RDF format uses the Dublin Core to describe as much of the interface as possible (because it's widely understood), with some extensions to describe the output dtd and input parameters / POSTed content.

The problem of describing XML-PRC in this way is that XML-RPC is very flexible - for example, because parameters are not specified by simple (and fixed) name/value pairs, or even a fixed schema for each function, the comments describing the input and output are very important.

This is RDF interface description is generated at - please excuse the formatting: Mail to the Future info@userland.coasdm/<;/dc:Creator> email, frontier, future, mail, send The Mail to the Future app is a hybrid website/application that runs from a Frontier 6 guest database. It supports three ways to connect, the HTML interface, a limited dynamic XML interface and a full-featured XML-RPC interface. The XML-RPC interface is key because it will allow developers working in other environments to build customized interfaces for this service, and will serve as a prototype for similar multiple-interface web applications. UserLand Software<;/dc:Source> text/xml<;/dc:Identifier> english HTTP POST<;/tree:OutputType> Free None<;/tree:UrlParameterExpression> There are five procedures you can call thru the XML-RPC interface. mailToTheFuture.addMessage (username, password, msgstruct) Adds a message to usernames queue. username must be the email address of a registered user. password must be that users password. msgstruct is a XML-RPC containing the following elements: dateTime, messageBody, receiverMailAddress, subject. A new message is created in the user's queue. It returns the size of the users queue, encoded as a string. mailToTheFuture.deleteMessage (username, password, n) Deletes the nth message in the users queue. Returns the empty string. If the users queue doesnt have an nth element, it s. mailToTheFuture.getAllMessages (username, password) Returns the entire queue for the user in a single . mailToTheFuture.getMessage (username, password, msgnum) Returns a single message as a . mailToTheFuture.setMessage (username, password, msgnum, msgstruct) Takes a and assigns it to the indicated message. This call allows a remote script to edit a MTTF message. mailToTheFuture.getMessageCount (username, password) Returns a number encoded as a string saying how many messages there are in the users queue. Yes XML snippet specified by DTD/Schema

This page was archived on 6/13/2001; 4:51:02 PM.

© Copyright 1998-2001 UserLand Software, Inc.