[JDEV] Rich Text in Messages

[Max Horn]

At 11:02 Uhr -0500 11.12.2000, tcharron wrote:
>   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.. :-)


It is even more difficult: the client behind a resource could change, 
and you wouldn't notice it.
In fact, Feature negotiation has been discussed over and over again 
in the past, but so far no usable solution has been found, AFAIK. 
Re-polling every n seconds is no solution, either, obviously, as it 
would cause tremondous network traffic...
A possibility would be to requery on every presence change...

But even this does not solve all problems: you did not take into 
account offline storage! If the user is offline, there is no way to 
do feature negotiation. So, what to do then?


Max
-- 
-----------------------------------------------
Max Horn
International C/C++/Internet Development

email: <mailto:max at quendi.de>
   web: <http://www.quendi.de>
phone: (+49) 6151-494890