On Tue, 22 Feb 2005 23:17:04 +0100, Fabio Forno <[EMAIL PROTECTED]> wrote: > Matthias Wimmer wrote: > > > Don't wrap your messages in <route/> elements ... you cannot "route" a > > packet to another server s <route/> elements are not allowed on s2s > > links. Just send the <message/> element. > > I'm realizing that I don't know enough about <route/> packets... If I > send a bare <message/> from the component (using the jabber:client > namespace, is it ok?) the message just disappear whithin the router.
Route messages are proprietary to some implementations of jabber servers. They exist solely to 'wrap' stanzas so that a componentized architecture can distribute them around without overwriting the existing to/from on the stanza. For example, systems with a separate client connection handling piece could use something like a 'route' stanza to deliver the message to a particular client address on the c2s piece, without having to modify (and later revert) attributes on the message itself in some fashion. Even within systems which use this type of routing stanza, it is my experience that most components will automatically return an error when presented with them. -David Waite _______________________________________________ jdev mailing list [email protected] http://mail.jabber.org/mailman/listinfo/jdev
