[JDEV] Rich Text in Messages

[tcharron]

From: "David Waite" <dwaite at jabber.com>
To: <jdev at jabber.org>
Subject: Re: [JDEV] Rich Text in Messages
> of course, the main reasons for the dual message approach are:
> 1. Lack of Feature Negotiation

  As said prior, an extention of the version namespace could fix this.
Rather simple extention, with minimal changes required..

> 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.

  Hrm, this one is interesting.  Thats a darned good point.  I'm not sure I
agree with "a) should bounce if that resource is not available b) should not
get redirected to another resource, ever.", becouse this would really hinder
the idea of univeral access.  At the same time, many messages SHOULD only go
to a given resource.  I may not want constant, real time stock updates going
to me PAGER, but I would to, lets say, my WinJab or Gabber client.

  Should messages have an additional attribute designating if they should be
routed or not?