Jabber server

There’s now a test Jabber server at test.nomic.net:5222. You can connect to
it by running the Player with the option “-DenableJabber=true”.

However:

  1. There are clearly some things still to be worked out on our end. When I
    tried to connect, I immediately got an exception, reported here:

sourceforge.net/tracker/?func=d … tid=594231

  1. I’m unimpressed in various ways with Openfire, already. Their documentation
    is poor. (E.g., they neglect to tell you what ports you need to open in your
    firewall, which is a necessary piece of information if you want your XMPP
    server to be accessible. There is also nothing anyplace which explains that
    you have to restart Openfire after you create the admin account in order to be
    able to log in with it, and the errors in the logs make it look like you’re
    just mistyping your password.) They don’t seem to be sufficiently together to
    have a proper Fedora RPM (the one they have on their site for download is a
    monster, as it supplies all of its own dependencies rather than use anything
    sufficiently new which is already on the system) and didn’t show much interest
    in working with two Fedora maintainers who offered to help with packaging).
    That makes the maintenance burden for us higher, since then we can’t rely on
    Fedora’s maintainers to keep Openfire up to date for us. They also seem not to
    be the XMPP server that the OSS community has coalesced around—I see way
    more talk about jabberd2 and ejabberd than Openfire. It looks like Openfire is
    going to suck up a gargantuan amount of RAM, as well.

If all we need is a standards-compliant XMPP server, I’d be all for switching
to something else.

The whole point of moving to Jabber is to make Vassal available to be run by anyone on any compliant Jabber server, so it should not matter which implementation we use for the offical ‘VASSAL’ server.

B.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Thus spake “Brent Easton”:

Yeah, then I’m going to hunt around a bit for a better one.

Anyway, this one is running right now, so I’m not the bottleneck anymore
(for now, on this particular issue). :slight_smile:


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

I have fixed this in trunk@6044. Can connect to the server now. That’s got me going.

Thanks.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)