On Thu, Apr 14, 2011 at 12:24 AM, john pradeep <[email protected]> wrote: > Having started to use Vysper for sometime, I am very interested in > contributing to the project, I was going through the core components of > vysper and the design was very elegant to understand it quickly!
Welcome onboard :-) > I don't know how to start with the contribution, but I observed a JIRA Item > - https://issues.apache.org/jira/browse/VYSPER-14 which I thought I will > pick up as my first task. > > If I am not wrong, I couldn't see a configuration framework for Vysper > so I thought of the below Idea at the top of my head. Right, Vysper currently uses a static set up. As for dynamically changing configuration in runtime, we need to consider the complexity of our code. That said, I think having decent support for introspecting a running server with JMX would be nice. I'm not yet convinced about dynamically changing the configuration of a running servers. But, others might disagree :-) As for the JIRA issue, I interpret that as having an option in our API/Spring support to configure thread pools. That's probably something we should expose on TCPEndpoint to be settable before the endpoint is started. Also, in this area of server configuration, we got the Service Administration spec that Bernd started working on: http://xmpp.org/extensions/xep-0133.html I'm sure Bernd would be happy to get some helping hands in this implementation :-) Also, picking a XEP that we do not yet support is a pretty nice way of learning how Vysper works in relation to the XMPP specs. /niklas
