Binary Lexical Octet Ad-hoc Transport Protocol
-
A [dated] RFC for enxcapsulating IP and TCP in XML. I can't help but think of Microsoft and C#... Binary Lexical Octet Ad-hoc Transport[^]. Jeff
-
A [dated] RFC for enxcapsulating IP and TCP in XML. I can't help but think of Microsoft and C#... Binary Lexical Octet Ad-hoc Transport[^]. Jeff
Have you picked up on the connection between the date of the Memo and the acronym?
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
-
Have you picked up on the connection between the date of the Memo and the acronym?
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”
Hi Henry,
Henry Minute wrote:
Have you picked up on the connection
Yes. But it seems that it went over the head of C#... JW
-
A [dated] RFC for enxcapsulating IP and TCP in XML. I can't help but think of Microsoft and C#... Binary Lexical Octet Ad-hoc Transport[^]. Jeff
I especially like that: The payload element bears special attention. Due to the character set restrictions of XML, the payload of IP datagrams (which MAY contain arbitrary data) MUST be encoded for transport. This RFC REQUIRES the contents of the payload to be encoded in the base-64 encoding of RFC 2045 [RFC2045], but removes the requirement that the encoded output MUST be wrapped on 76-character lines. That was the first time I gave up on XML: havign to base64 - encode the payload. ("Simple" string encoding was a bad idea for one reason or another)