Dnia 2009-05-31, nie o godzinie 00:18 -0400, Paul Fox pisze: > 1.) Multi-user chat: why is it maintained as a separate library?
It's a separate server component connecting using component protocol, thus it is server independent and it is working with every server implementation, not with jabberd2 only. > I have to imagine there would be a fair amount of redundant code > involved. Not really. It is based on jabberd 1.x code. > Is there any plan to integrate this functionality into the server? Not really. jabberd2 is an XMPP server implementation, not MUC service implementation. > How well/easily does the existing component work? It's pretty stable and standard compliant. > 2.) http binding: I see that it is on the wishlist. Is anyone working > on it at present? AFAIK no one is working on it now. > Would it be a task a programmer fairly knowledgeable but with only a > small amount of coding experience could attempt? It is an opportunity to learn. Both coding and jabberd2 internals (which is a pretty interesting piece of engineering). I will gladly help and guide anyone starting to work with jabberd2 codebase. -- Tomasz Sterna Instant Messaging & EDI Consultant Open Source Developer http://tomasz.sterna.tv/ http://www.xiaoka.com/ -- To unsubscribe send a mail to [email protected]
