On Sunday, January 17, 2010, Norman Maurer <[email protected]> wrote: > Ok, I have now every implementation in place except one for > nntpserver. To be hornest I would be +1 for just remove the whole > nntpserver stuff. IMHO, its just a left over from the "old days" and > not maintained anyway. I don't think anyone is using it anyway. So > what about just remove the whole nntpserver stuff . If we really find > some usecase we can "merge" it back later.
I have cool stuff I'd like to do with NNTP and it gives James that little bit extra that other servers don't have. However, for a while I've been planning to pull out NNTP into a self contained product. Now James 3 uses Spring I should be able to factor out an independent NNTP product and then people interested in it can just drop and configure using Spring. If people are in favour I should be able to do this pretty quick... Opinions? Robert > > > Bye, > Norman > > 2010/1/17 Mario Zsilak <[email protected]>: >> Nice :) >> >>>-----Ursprüngliche Nachricht----- >>>Von: [email protected] [mailto:[email protected]] >>>Im Auftrag von Norman Maurer >>>Gesendet: Sonntag, 17. Januar 2010 12:30 >>>An: James Developers List >>>Betreff: Removing Cornerstone sockets in favor of MINA >>> >>>Hi all, >>> >>>as you maybe already noticed, I'm currently workin on writting async >>>implementations of all networkserver using mina. This will give us the >>>possibility to remove cornerstone sockets and "just" use MINA. I think >>>thats the right way to go... >>> >>>WDYT ? >>> >>>The only server component which gives me headaches atm is the >>>imapserver. But I need to dig a bit deeper in the code to understand >>>how we can use it with MINA ... >>> >>> >>>Bye, >>>Norman >>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: [email protected] >>>For additional commands, e-mail: [email protected] >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
