Thu, 3 Jan 2002 15:05:03 -0800
The big win seems to be that you can write a
much effort. Downsides include "hey, everybody
has SOAP already".
Begin forwarded message:
> From: "S. Alexander Jacobson" <firstname.lastname@example.org>
> Date: Thu Jan 03, 2002 01:36:09 PM US/Pacific
> To: email@example.com, SOAP <SOAP@DISCUSS.DEVELOP.COM>, <xml-
> firstname.lastname@example.org>, <email@example.com>, <firstname.lastname@example.org>,
> <Greg.Vaudreuil@Octel.Com>, <email@example.com>,
> <ELevinson@Accurate.com>, <firstname.lastname@example.org>, <email@example.com>
> Subject: ANN: MIME-RPC Protocol Draft and Python Implementation
> MIME-RPC is a protocol for interapplication
> messaging and object serialization. I designed
> it to simplify the tasks that people currently
> use SOAP, XML-RPC, CGI, or Servlets to
> accomplish (and to avoid all the controversy
> surrounding XML embedding and parsing that are
> part of many of these discussions). Points to note:
> * It works with the millions of already deployed
> web apps and web browsers (without plugins)
> * It handles all Internet data including Unicode,
> JPEG, XML, etc.
> * It works over both HTTP and SMTP (web and
> * It protects application programmers from wire
> level concerns.
> * It provides complete interlanguage object
> serialization (cyclic refs.) as well as
> interlanguage messaging
> * It supports two way communication over
> client/server connections
> * It is easy to implement.
> * It doesn't require an extra XML parser when
> your application doesn't need one.
> * Its specification is short and unambiguous.
> * It leverages existing transport layer features
> like encryption, proxying, asynchrony,
> streaming/chunking, etc.
> Please check out www.mime-rpc.com, and tell me
> your thoughts. Note, this is still a draft so be
> gentle. A discussion list on issues related to
> MIME-RPC is at
> S. Alexander Jacobson i2x Media
> 1-212-787-1814 voice 1-603-288-1280 fax