[JDEV] Rich Text in Messages

[David Waite]

of course, the main reasons for the dual message approach are:
1. Lack of Feature Negotiation
2. Lack of 'true' directed messages. Messages sent to a specific user
resource a) should bounce if that resource is not available b) should
not get redirected to another resource, ever.

Because of 1., we send the additional data and let the other client
'hint' on whether the data is being understood.
Because of 2, there is *always* the possibility that a client will go
offline, and your messages will all of a sudden fall on another resource
(say, a pager) which cannot make sense of a pure XHTML / FTML / etc.
message.

I of course would prefer to fix the problems rather than work around
them, as they are already debilitating for some of my pet projects
(whiteboard, gametrans)

-David Waite

Todd Bradley wrote:

> > 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,
>
> That's for sure.  It's not very future-friendly.  What happens
> when FTML (FooTextMarkupLanguage) becomes the rage next year?
> Will clients then send ASCII, XHMTL, and FTML messages, all
> three, in hopes at least one can be understood by the client
> on the other end?
>
> Also, you're only considering the client's issues.  Consider
> the Jabber servers processing IBM's employee-to-employee and
> employee-to-customer traffic.  Let's say that'll be 10,000,000
> message per day in 2002, a farm of 20 quad processor servers.
> How feasible will it be to double (or triple) the size of those
> Jabber messages, just so your users can send bold text?
>
> Todd.
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev