RFC 3529: Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)
In plain English — editorial summary, not part of the RFC
Markup Language-Remote Procedure Calling protocol that works over the Internet. It defines an XML format for messages that are transfered between clients and servers using HTTP. An XML-RPC message encodes either a procedure to be invoked by the server, along with the parameters to use in the invocation, or the result of an invocation. Procedure parameters and results can be scalars, numbers, strings, dates, etc.; they can also be complex record and list structures. This document specifies a how to use the Blocks Extensible Exchange Protocol (BEEP) to transfer messages encoded in the XML-RPC format between clients and servers. This memo defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC3529
- Published
- April 2003
- Authors
- W. Harold
- Status
- EXPERIMENTAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 15
- Also known as
- —
- Updated by:
- RFC 8553
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3080The Blocks Extensible Exchange Protocol CoreCurrent
March 2001
- RFC 3620The TUNNEL ProfileUpdated
October 2003
- RFC 3767Securely Available Credentials ProtocolUpdated
June 2004
- RFC 3081Mapping the BEEP Core onto TCPCurrent
March 2001
- RFC 2683IMAP4 Implementation RecommendationsUpdated
September 1999
- RFC 3629UTF-8, a transformation format of ISO 10646Current
November 2003
- RFC 3423XACCT's Common Reliable Accounting for Network Element (CRANE) Protocol Specification Version 1.0Current
November 2002
- RFC 3685SIEVE Email Filtering: Spamtest and VirusTest ExtensionsObsoleted
February 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?