[JDEV] Rich Text in Messages
tcharron
tcharron at ductape.net
Mon Dec 11 10:02:50 CST 2000
This is a damned fine idea, and starts down the road of feature
negotiation. This capability listing could basically just say what x tags
this client supports. It's taken for granted that all client support the
basics, such as raw text in the message, etc. If there are ADDITIONAL
things that the client can take care of, they could be used, but wouldn;t be
required.
The only issue I could see is this will *ONLY* work if the message is
directed to a resource. Different resources (clients, really) have
different capabilities. When they are not online, you would HAVE to send it
in both formats. I don;t see XHTML being displayed on my pager any time
soon.. :-)
From: "Michael F Lin" <mflin at us.ibm.com>
To: <jdev at jabber.org>
Subject: Re: [JDEV] Rich Text in Messages
> Ryszard (any everyone),
> For your day-to-day Jabber chats I don't think sending two versions of the
> message is a huge problem, even on 19.2kbps wireless connections. I do
> accept that it is not the most efficient way to go about this, however,
and
> so I propose that we extend jabber:iq:version to support something along
> these lines:
<SNIP>
> <capabilities>
> <xhtml/>
> <revenge/>
More information about the JDev
mailing list