scott at tranzoa.com
Wed Aug 11 11:17:22 CDT 1999
I've added all of the suggestions in one form or another. My page should be
updated in just a couple seconds after I send this post.
* Jeremie translated into ASCII [Wed, Aug 11, 1999 at 10:58:26AM -0500][<Pine.LNX.4.10.9908111034190.26114-100000 at lor.jeremie.com>]
> Great work!
> Only thing I can suggest is that you might want to specifically mention
> escaping, that the contents of a <mime/> tag are normal XML CDATA and need
> to be escaped properly: http://www.w3.org/TR/REC-xml#syntax In the
> example the content-type="message/jabber" would need to have all of it's <
> and > characters escaped :)
> The server, even as it stands now in 0.6, should already properly pass
> through the entire <mime/> chunk from one client to another, and it should
> continue to support that transparency.
> You might also want to mention that multiple <mime/> tags can be mixed
> within the content in the <say/>, this might be more appropriate in places
> instead of a multipart message, but both are useful and supported.
> The only thing I'd like to make clear to client authors is: It's
> suggested that they support <mime/> for the benifit of their users as
> fully as possible, but it is not required of them to do so. Partial
> support of at least text/plain and text/html is *highly* reccomended if
> nothing else.
> On Wed, 11 Aug 1999, Scott Robinson wrote:
> > Fine then. Let me up the ante.
> > http://dsn.itgo.com/MIME.html
> > Scott.
> > _______________________________________________
> > jdev mailing list
> > jdev at jabber.org
> > http://mailman.jabber.org/listinfo/jdev
> jdev mailing list
> jdev at jabber.org
More information about the JDev