Meta tags:

Headings (most frequently used words):

xml, rpc, specification,

Text of the page (most frequently used words):
the (87), value (36), and (34), xml (29), can (25), type (19), string (17), struct (17), not (16), any (15), for (15), rpc (14), userland (13), that (13), contain (13), this (12), name (12), example (12), characters (11), params (11), content (11), fault (10), member (10), other (9), server (9), which (9), single (9), array (9), copyright (8), may (8), are (8), data (8), number (8), methodresponse (8), contains (8), request (8), specified (7), true (7), boolean (7), response (7), all (6), protocol (6), what (6), procedure (6), also (6), could (6), text (6), param (6), must (6), 1998 (5), specification (5), updated (5), there (5), you (5), element (5), allowed (5), how (5), with (5), numeric (5), format (5), structure (5), http (5), length (5), methodcall (5), methodname (5), software (4), non (4), list (4), two (4), whitespace (4), only (4), plus (4), one (4), containing (4), frontier (4), int (4), here (4), inc (3), document (3), information (3), herein (3), provided (3), including (3), implement (3), its (3), works (3), above (3), from (3), base64 (3), should (3), faultcode (3), faultstring (3), distinct (3), structures (3), post (3), used (3), binary (3), range (3), point (3), values (3), deal (3), infinity (3), minus (3), leading (3), signed (3), zero (3), false (3), environments (3), easy (3), body (3), file (3), 200 (3), date (3), winnt (3), version (3), parameters (3), sub (3), item (3), uri (3), rpc2 (3), 2004 (2), contained (2), warranties (2), implied (2), but (2), limited (2), will (2), rights (2), such (2), notice (2), these (2), commercial (2), without (2), copied (2), derivative (2), implementation (2), distributed (2), 2003 (2), dates (2), below (2), 1999 (2), timezone (2), datetime (2), iso8601 (2), members (2), than (2), global (2), languages (2), python (2), codes (2), level (2), standards (2), believe (2), needs (2), within (2), message (2), discussion (2), group (2), does (2), order (2), keys (2), foo (2), bar (2), equivalent (2), strings (2), encoded (2), legal (2), syntax (2), floating (2), represented (2), time (2), followed (2), integers (2), zeros (2), integer (2), allow (2), leave (2), out (2), implemented (2), wanted (2), simple (2), able (2), call (2), have (2), first (2), connection (2), close (2), fri (2), jul (2), gmt (2), elements (2), named (2), correct (2), lower (2), recursive (2), described (2), mix (2), four (2), each (2), indicated (2), double (2), scalars (2), table (2), has (2), executes (2), incoming (2), slash (2), payload (2), user (2), agent (2), host (2), header (2), handling (2), requests (2), route (2), internet (2), dave (2), 2011, scripting, news, trademark, posted, pacific, basis, disclaims, express, warranty, use, infringe, merchantability, fitness, particular, purpose, modified, way, removing, references, organizations, further, while, restrictions, apply, written, claim, ownership, made, describes, party, purposes, royalty, license, fee, permissions, granted, perpetual, revoked, successors, assigns, translations, furnished, others, comment, otherwise, explain, assist, prepared, published, whole, part, restriction, kind, paragraphs, included, copies, reserved, disclaimer, changed, removed, ascii, definition, additions, assumed, utc, localtime, don, assume, documentation, assumptions, makes, about, timezones, faultcodes, they, mapped, exceptions, like, java, implementer, higher, specify, those, flexible, enough, reasonable, transfer, accomodated, strongly, please, keep, words, preserve, structs, printable, null, hold, arbitrary, chunk, except, encode, doubles, exponent, representation, negative, decimal, notation, period, allowable, dependent, sign, bit, include, beginning, collapsed, permitted, just, preceeded, interchanged, yes, some, coercion, mean, send, your, intent, possibly, misunderstood, section, says, confusing, cannot, executed, successfully, options, either, why, word, sentence, following, questions, came, was, being, quickly, adapted, run, operating, systems, clean, extensible, very, possible, html, coder, look, understand, doing, modify, work, second, try, discoverability, goal, lay, compatible, foundation, across, different, new, power, beyond, capabilities, cgi, interface, firewall, watch, posts, whose, firewalls, strategies, goals, 426, too, many, both, present, unless, error, always, return, 158, south, dakota, arrays, types, illustrates, names, egypt, lowerbound, upperbound, 139, ew91ignhbid0ihjlywqgdghpcye, 19980717t14, 214, precision, hello, world, byte, tag, nesting, inside, tags, listed, scalar, script, cell, database, path, hierarchy, folders, files, method, called, identifier, upper, case, underscore, dot, colon, entirely, decide, interpret, line, empty, calls, however, help, code, handles, telling, responder, requirements, betty, com, 181, examples, getstatename, numbers, etc, complex, record, returns, formatted, remote, calling, over, overview, page, provides, implementor, technical, explanation, see, newbies, documents, tue, jun, winer, opml, rss, directory, mail, spec, cross, platform, computing, based,

Text of the page (random words):
xml rpc specification simple cross platform distributed computing based on the standards of the internet spec mail list directory c c rss opml xml dave xml rpc specification tue jun 15 1999 by dave winer updated 6 30 03 dw updated 10 16 99 dw updated 1 21 99 dw this specification documents the xml rpc protocol implemented in userland frontier 5 1 for a non technical explanation see xml rpc for newbies this page provides all the information that an implementor needs overview xml rpc is a remote procedure calling protocol that works over the internet an xml rpc message is an http post request the body of the request is in xml a procedure executes on the server and the value it returns is also formatted in xml procedure parameters can be scalars numbers strings dates etc and can also be complex record and list structures request example here s an example of an xml rpc request post rpc2 http 1 0 user agent frontier 5 1 2 winnt host betty userland com content type text xml content length 181 xml version 1 0 methodcall methodname examples getstatename methodname params param value i4 41 i4 value param params methodcall header requirements the format of the uri in the first line of the header is not specified for example it could be empty a single slash if the server is only handling xml rpc calls however if the server is handling a mix of incoming http requests we allow the uri to help route the request to the code that handles xml rpc requests in the example the uri is rpc2 telling the server to route the request to the rpc2 responder a user agent and host must be specified the content type is text xml the content length must be specified and must be correct payload format the payload is in xml a single methodcall structure the methodcall must contain a methodname sub item a string containing the name of the method to be called the string may only contain identifier characters upper and lower case a z the numeric characters 0 9 underscore dot colon and slash it s entirely up to the server to decide how to interpret the characters in a methodname for example the methodname could be the name of a file containing a script that executes on an incoming request it could be the name of a cell in a database table or it could be a path to a file contained within a hierarchy of folders and files if the procedure call has parameters the methodcall must contain a params sub item the params sub item can contain any number of param s each of which has a value scalar value s value s can be scalars type is indicated by nesting the value inside one of the tags listed in this table tag type example i4 or int four byte signed integer 12 boolean 0 false or 1 true 1 string string hello world double double precision signed floating point number 12 214 datetime iso8601 date time 19980717t14 08 55 base64 base64 encoded binary ew91ignhbid0ihjlywqgdghpcye if no type is indicated the type is string struct s a value can also be of type struct a struct contains member s and each member contains a name and a value here s an example of a two element struct struct member name lowerbound name value i4 18 i4 value member member name upperbound name value i4 139 i4 value member struct struct s can be recursive any value may contain a struct or any other type including an array described below array s a value can also be of type array an array contains a single data element which can contain any number of value s here s an example of a four element array array data value i4 12 i4 value value string egypt string value value boolean 0 boolean value value i4 31 i4 value data array array elements do not have names you can mix types as the example above illustrates arrays s can be recursive any value may contain an array or any other type including a struct described above response example here s an example of a response to an xml rpc request http 1 1 200 ok connection close content length 158 content type text xml date fri 17 jul 1998 19 55 08 gmt server userland frontier 5 1 2 winnt xml version 1 0 methodresponse params param value string south dakota string value param params methodresponse response format unless there s a lower level error always return 200 ok the content type is text xml content length must be present and correct the body of the response is a single xml structure a methodresponse which can contain a single params which contains a single param which contains a single value the methodresponse could also contain a fault which contains a value which is a struct containing two elements one named faultcode an int and one named faultstring a string a methodresponse can not contain both a fault and a params fault example http 1 1 200 ok connection close content length 426 content type text xml date fri 17 jul 1998 19 55 02 gmt server userland frontier 5 1 2 winnt xml version 1 0 methodresponse fault value struct member name faultcode name value int 4 int value member member name faultstring name value string too many parameters string value member struct value fault methodresponse strategies goals firewalls the goal of this protocol is to lay a compatible foundation across different environments no new power is provided beyond the capabilities of the cgi interface firewall software can watch for posts whose content type is text xml discoverability we wanted a clean extensible format that s very simple it should be possible for an html coder to be able to look at a file containing an xml rpc procedure call understand what it s doing and be able to modify it and have it work on the first or second try easy to implement we also wanted it to be an easy to implement protocol that could quickly be adapted to run in other environments or on other operating systems updated 1 21 99 dw the following questions came up on the userland discussion group as xml rpc was being implemented in python the response format section says the body of the response is a single xml structure a methodresponse which can contain a single params this is confusing can we leave out the params no you cannot leave it out if the procedure executed successfully there are only two options either a response contains a params structure or it contains a fault structure that s why we used the word can in that sentence is boolean a distinct data type or can boolean values be interchanged with integers e g zero false non zero true yes boolean is a distinct data type some languages environments allow for an easy coercion from zero to false and one to true but if you mean true send a boolean type with the value true so your intent can t possibly be misunderstood what is the legal syntax and range for integers how to deal with leading zeros is a leading plus sign allowed how to deal with whitespace an integer is a 32 bit signed number you can include a plus or minus at the beginning of a string of numeric characters leading zeros are collapsed whitespace is not permitted just numeric characters preceeded by a plus or minus what is the legal syntax and range for floating point values doubles how is the exponent represented how to deal with whitespace can infinity and not a number be represented there is no representation for infinity or negative infinity or not a number at this time only decimal point notation is allowed a plus or a minus followed by any number of numeric characters followed by a period and any number of numeric characters whitespace is not allowed the range of allowable values is implementation dependent is not specified what characters are allowed in strings non printable characters null characters can a string be used to hold an arbitrary chunk of binary data any characters are allowed in a string except and which are encoded as and a string can be used to encode binary data does the struct element keep the order of keys or in other words is the struct foo 1 bar 2 equivalent to bar 2 foo 1 or not the struct element does not preserve the order of the keys the two structs are equivalent can the fault struct contain other members than faultcode and faultstring is there a global list of faultcodes so they can be mapped to distinct exceptions for languages like python and java a fault struct may not contain members other than those specified this is true for all other structures we believe the specification is flexible enough so that all reasonable data transfer needs can be accomodated within the specified structures if you believe strongly that this is not true please post a message on the discussion group there is no global list of fault codes it is up to the server implementer or higher level standards to specify fault codes what timezone should be assumed for the datetime iso8601 type utc localtime don t assume a timezone it should be specified by the server in its documentation what assumptions it makes about timezones additions base64 type 1 21 99 dw updated 6 30 03 dw removed ascii from definition of string changed copyright dates below to 1999 2003 from 1998 99 copyright and disclaimer copyright 1998 2003 userland software all rights reserved this document and translations of it may be copied and furnished to others and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared copied published and distributed in whole or in part without restriction of any kind provided that the above copyright notice and these paragraphs are included on all such copies and derivative works this document may not be modified in any way such as by removing the copyright notice or references to userland or other organizations further while these copyright restrictions apply to the written xml rpc specification no claim of ownership is made by userland to the protocol it describes any party may for commercial or non commercial purposes implement this protocol without royalty or license fee to userland the limited permissions granted herein are perpetual and will not be revoked by userland or its successors or assigns this document and the information contained herein is provided on an as is basis and userland disclaims all warranties express or implied including but not limited to any warranty that the use of the information herein will not infringe any rights or any implied warranties of merchantability or fitness for a particular purpose copyright 2004 2011 scripting news inc copyright 1998 2004 userland software inc xml rpc is a trademark of userland software inc posted 6 15 99 12 00 00 am pacific