idnits 2.17.1 draft-harold-beep-xmlrpc-03.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3529 5 Title: Using Extensible Markup Language-Remote Procedure 6 Calling (XML-RPC) in Blocks Extensible Exchange 7 Protocol (BEEP) 8 Author(s): W. Harold 9 Status: Experimental 10 Date: April 2003 11 Mailbox: wharold@us.ibm.com 12 Pages: 15 13 Characters: 23312 14 Updates/Obsoletes/SeeAlso: None 16 I-D Tag: draft-harold-beep-xmlrpc-03.txt 18 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3529.txt 20 XML-RPC is an Extensible Markup Language-Remote Procedure Calling 21 protocol that works over the Internet. It defines an XML format for 22 messages that are transfered between clients and servers using HTTP. 23 An XML-RPC message encodes either a procedure to be invoked by the 24 server, along with the parameters to use in the invocation, or the 25 result of an invocation. Procedure parameters and results can be 26 scalars, numbers, strings, dates, etc.; they can also be complex 27 record and list structures. 29 This document specifies a how to use the Blocks Extensible Exchange 30 Protocol (BEEP) to transfer messages encoded in the XML-RPC format 31 between clients and servers. 33 This memo defines an Experimental Protocol for the Internet community. 34 It does not specify an Internet standard of any kind. Discussion and 35 suggestions for improvement are requested. Distribution of this memo 36 is unlimited. 38 This announcement is sent to the IETF list and the RFC-DIST list. 39 Requests to be added to or deleted from the IETF distribution list 40 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 41 added to or deleted from the RFC-DIST distribution list should 42 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 44 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 45 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 46 help: ways_to_get_rfcs. For example: 48 To: rfc-info@RFC-EDITOR.ORG 49 Subject: getting rfcs 51 help: ways_to_get_rfcs 53 Requests for special distribution should be addressed to either the 54 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 55 specifically noted otherwise on the RFC itself, all RFCs are for 56 unlimited distribution.echo 57 Submissions for Requests for Comments should be sent to 58 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 59 Authors, for further information.