--xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
> we are thinking about a new protocol for inter-MUD-communication > based on at least the xmpp-core-protocol. a Mud provides communication > facilities to serveral users so we thought about integration of the > jabber server into the mudlib or using a external jabber server. > my favorite would be an external server but then the qeustion is: > do we need a tcp-connection for every user from mud to server=20 > or is it possible to use a single connection? in the first case > the jid would be [EMAIL PROTECTED], in the second=20 > [EMAIL PROTECTED]/player_name. It it possible to use more than one=20 > jid/resource with a single tcp-conn? The first way ([EMAIL PROTECTED]) is probably what you want. You can do this by writing a server component which connects to a Jabber router and handles all packets destined for "mud_name". Your component would then map the Jabber packets into appropriate functions for your MUD (API calls or whatever). (This method is almost exactly the same as a "transport" to a foreign IM service). If you have access to the code for your MUD, you might want to consider having your MUD connect directly to a Jabber router, or even better, have it implement s2s (dialback) so that it can be on the Jabber network on its own. Hell, you could even expand this into a complete Jabber-based interface to the MUD (of course still allowing users to connect to the normal telnet interface). Something like groupchat/conference/muc might be useful here. This is a cool idea. One of the things I did early on in my Jabber days was look at how Jabber might be used as an interface to a Ew-too talk server. I didn't go very far with it, but it was very similar to what you're talking about doing. Feel free to contact me to chat about this if you like - I'd like to see what you come up with :) Rob. --=20 Robert Norris GPG: 1024D/FC18E6C2 Email+Jabber: [EMAIL PROTECTED] Web: http://cataclysm.cx/ --xHFwDpU9dbj6ez1V Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/E5FyWb13Z/wY5sIRAuZKAJ41WT+s9UCbvNvPfzs/WhY5bc7y4QCfUfIq irtuEZ/AAxMk7xcX+pU1Sfk= =/BeF -----END PGP SIGNATURE----- --xHFwDpU9dbj6ez1V-- _______________________________________________ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
