Monday, June 14, 2010
3023 RFC - A Mechanism for Creating More Specific Identifiers for XML Identified as, "text/xml"
http://www.ietf.org/rfc/rfc3023.txt
The value of the Content-Type header is constant within XML-RPC; it is the Internet media type for XML, "text/xml" XML-RPC appeared before RFC 3023, which specifies a mechanism for creating more specific identifiers for xml types. If one builds XML-RPC implementations that accept other flavors of XML identified as, "text/xml"( as well as XML-RPC over the same port), one will need to identify XML-RPC messages by the methodCall root element.
The value of the Content-Type header is constant within XML-RPC; it is the Internet media type for XML, "text/xml" XML-RPC appeared before RFC 3023, which specifies a mechanism for creating more specific identifiers for xml types. If one builds XML-RPC implementations that accept other flavors of XML identified as, "text/xml"( as well as XML-RPC over the same port), one will need to identify XML-RPC messages by the methodCall root element.
Sunday, June 13, 2010
2045 RFC - Base64 Encoding for Binary attachments
http://www.ietf.org/rfc/rfc2045.txt
I came across the above link while I was reading about XML-RPC. As XML prohibits any character with an ordinal value lower than that of the space character( 32), commonly called control characters. Although, binary items, such as binary files, may contain these characters. The solution is to use an ASCII-based encoding of the binary object, and XML-RPC uses base-64 encoding.
I came across the above link while I was reading about XML-RPC. As XML prohibits any character with an ordinal value lower than that of the space character( 32), commonly called control characters. Although, binary items, such as binary files, may contain these characters. The solution is to use an ASCII-based encoding of the binary object, and XML-RPC uses base-64 encoding.
Subscribe to:
Comments (Atom)