> That being said, a XMPP server is really meaningless if you don't define > how much of XMPP you'd like to support. For a student project, I guess > XMPP-core, XMPP-IM [3] server side would already be a solid project. More > might hurt the success of the project.
Instead of creating (yet another) full XMPP server, how about creating something like a standalone MUC component. This requires implementing a part of an XMPP server, but certainly not everything from core and IM. I have had a situation where I would have really liked to set up a MUC conference server without running the full blown server. Or maybe, to have something more general, something that can take any component (like a transport, ...), and serve it standalone. I haven't given this much thought whether this technically makes sense or is possible at all, but from a user's perspective I think it would (cfr the MUC case). cheers, Remko
