Tony, >I do a fair amount of work with the guts of HTTP clients and servers, and >with other RFC-standard protocols, as well as custom protocols over TCP.
Me too (anyone want to license my ASN.1/BER routines?), but I was thinking of email and similar payloads attached to messages -- associate the dynamicarray data type with your application and your VB (or whatever) program can automatically open the data. You can embed your dynamic array in XML but you might need to be careful of the whitespace handling rules -- since whitespace appearing in a dynamic array is likely to be significant. Your would also need to be sure that the character set for your XML treated the MV delimiters correctly (which UTF8 does, I have no idea about other character sets). As for using text/plain, isn't that supposed to be 7 bit ASCII unless you specify a charset (RFC2646) and once you do will it be reliably interpreted? (In general I mean, obviously your own applications will handle the 8 bit text correctly). Not to mention the 998/78 characters per line limits (RFC2821/3676) which may insert line breaks into your data where you don't expect them -- a separate mime type is more likely to be encoded using base64 or quoted printable and hence avoid this problem. ---- The other reason I thought a registered mime type would be useful was as a psychological/political tool -- once you have a registered mime type it might be one bit easier for people to accept the data structure without going through the whole educational rigmarole every time someone else looks at an MV database and its data formats. Craig ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
