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. At first thought I don't see the value in a specialized type like this. The few client/server processors that would use it would need to implement specialized handling - or would ignore a content-type anyway. The exact same handling will be done for text/plain or text/xml, so why create a standard type that nets down to the same thing?
In a data exchange, compared to a browser, I'd prefer to see a Web Service wrap MV data in SOAP. If I'm not mistaken you should be able to pass dynamic arrays without problem, including chars 252-254. As long as the remote side understands the data then there's no unique content-type required. The only way I can see this of value is if someone writes a browser plug-in that accepts raw MV data and formats it. I don't see that happening at all, for many reasons. If you can present a couple good cases for applying a new type like this, I might come 180 degrees. Interesting thought tho... Tony > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Craig Bennett > Sent: Wednesday, June 16, 2004 9:34 PM > To: [EMAIL PROTECTED] > Subject: [U2] Mime Type: application/dynamicarray > > Hi All, > > I was just wondering idly if anyone had considered > registering a mime type for sending dynamic arrays? > > I'm all for sending XML etc, but if you are just sending to another U2 > system or your own Java/VB system parsing the dynamic array > is trivial and > it would be nice to be able to say "Check the ietf list, > there is a mime type registered.". > > I presume such a type would need to be registered by one of > IBM, RD etc but > if people think it is a good idea, I am happy to try and register it. ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
