[JDEV] Rich Text in Messages

[David Waite]

Of course, the reason it is 'feature negotiation' rather than a feature mask is
that different features are desirable in different circumstances. If there was
a Foo Text Markup Language, it is very possible that some traffic may be better
formed in it than in xhtml.  In the end, both would be required. Also, feature
sets may not be static throughout a client session (read: dynamically loadable
modules/plugin arch)

In what circumstances would feature negotiation not work due to presence? Am I
not correct in the assumption that even if another resource bumps an existing
one off due to name conflict, that the presence cycles to 'offline'? You also
can't change your resource without reauthenticating. In what circumstance would
you not know that a client has changed to a reduced featureset without having
them drop offline?

-David Waite

tcharron wrote:

> From: "Max Horn" <max at quendi.de>
> Subject: Re: [JDEV] Rich Text in Messages
> > 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...
>
>   Agreed.  No one has come up with an adaquate solution as of yet..
>
> > 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?
>
>     Once again, as my mind meanders.  Why couldn't the server detect these?
> The server will already know if the client changes.  Require the client send
> an IQ setting it's capabilities to the server.  Then the server notifies
> everyone of the new capabilities..
>
>     And if one wanted to go one step further, the whole idea of XML style
> sheets come into play.  If it was stated that all formated types needed an
> XSL stylesheet, and we incorperated one into the server, couldn't the server
> then reformat the information on the fly as needed?  Thus, I could be in
> WinJab, viewing something via XHTML, but then later login to my Web client,
> and have the server automatically display all my messages in HTML format,
> running the messages thru the XSL stylesheet processor?
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev