On Wed, Apr 16, 2008 at 10:45 AM, Gerolf Seitz <[EMAIL PROTECTED]> wrote: > Thanks. > Is there some kind of checklist to see which parts of the RFCs are already > supported? > Maybe have a listing of section/subsections which can be ticked: > > 7. Roster Retrieval and Management [ ] > 7.3 Roster retrieval [x] > 7.4 Adding a Roster Item [ ] > ... >
great idea! in the code there are some comments which indicate the relevant spec section. what about putting a special doclet tag or documenting attribute at the unit test which is covering a section. we could then generate the document you outlined above from this code. > I'm aware that vysper is still in it's infancy, but did you already think of > some > non-functional requirements like scalability and stuff? (of course it should > be > scalable to infinity ;) ) I have that in mind, but did no test yet. I try to do everything as stateless as possible. MINA (if done right) should give us scalability on the transport level. There are no threads started anywhere explicitly, except through the means of MINA and ExecutorService. I don't think the server scales yet, but I try to avoid anything which makes implementing scalabilty harder. Maybe some synchronized sections are missing. Dunno. Do you have more specific requirements or see areas where scalability could become a problem? Bernd --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
