Both. Unless you need any special delivery semantics you should be able to embed your custom namespace in <iq> or <message> tags, which will be passed to the server without any interference. If you do need any special semantics, or need to communitate with a non-XMPP network then writting a transport is probably a better bet than hacking the server code. It will also make your `secret project' more portable if you decide to use a different transport in the future.

GuruJ wrote:

David 'TheRaven' Chisnall wrote:

No, I actually did mean don't. Most protocol enhancements will not require any direct participation by the server, so you could use a generic jabberd. Your requirement of using windows on your server, however, means that you are likely to need to modify jabberd to get the kind of performance you are going to need. Of course if you do need the server to do something special then jabberd may still be the best option...


David, by this do you mean that any extensions to the server can be handled by jabber components, rather than through any changes to the server code itself? Or will jabber faithfully transmit 'custom' XML messages it receives on to clients, even if the server itself has no idea what the message means?

-- GuruJ.


_______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev



_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev

Reply via email to