Browse Prior Art Database

Using Extensible Markup Language-Remote Procedure Calling (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP) (RFC3529)

IP.com Disclosure Number: IPCOM000012310D
Original Publication Date: 2003-Apr-01
Included in the Prior Art Database: 2003-Apr-30
Document File: 16 page(s) / 24K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

W. Harold: AUTHOR

Abstract

XML-RPC is an Extensible 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 text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 12% of the total text.

Network Working Group                                          W. Harold

Request for Comments: 3529                                           IBM

Category: Experimental                                        April 2003

       Using Extensible Markup Language-Remote Procedure Calling

        (XML-RPC) in Blocks Extensible Exchange Protocol (BEEP)

Status of this Memo

   This memo defines an Experimental Protocol for the Internet

   community.  It does not specify an Internet standard of any kind.

   Discussion and suggestions for improvement are requested.

   Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

Abstract

   XML-RPC is an Extensible 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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . .  2

   2.  BEEP Profile Identification  . . . . . . . . . . . . . . . .  2

       2.1  Profile  Initialization . . . . . . . . . . . . . . . .  3

   3.  XML-RPC Message Packages . . . . . . . . . . . . . . . . . .  4

   4.  XML-RPC Message Exchange . . . . . . . . . . . . . . . . . .  5

   5.  URL Schemes  . . . . . . . . . . . . . . . . . . . . . . . .  5

       5.1  The xmlrpc.beep URL Scheme. . . . . . . . . . . . . . .  5

            5.1.1 Resolving IP/TCP Address  Information . . . . . .  6

       5.2  The xmlrpc.beeps URL Scheme . . . . . . . . . . . . . .  7

   6.  Initial Registrations  . . . . . . . . . . . . . . . . . . .  9

       6.1  Registration: The XML-RPC Profile . . . . . . . . . . .  9

       6.2  Registration: The xmlrpc.beep URL Scheme. . . . . . . .  9

Harold                        Experimental                      [Page 1]

RFC 3529                 Using XML-RPC in BEEP                April 2003

       6.3  Registration: The xmlrpc.beeps URL Scheme . . . . . . . 10

       6.4  Registration: The System (Well-Known) TCP port number

            for XML-RPC over BEEP . . . . . . . . . . . . . . . . . 10

   7.  Security Considerations  . . . . . . . . . . . . . . . . . . 11

   8.  References . . . . . ....