Re: Javadoc & commits

2008-06-11 Thread Tuure Laurinolli
[EMAIL PROTECTED] wrote: If you are following the commit log, everybody is urging for getting more and more code covered with Javadoc and internal code documentation. What is this commit log you're talking about? I can't see any mention of it on the web page.

Re: Javadoc & commits

2008-06-11 Thread Emmanuel Lecharny
[EMAIL PROTECTED] wrote: Hi, If you are following the commit log, everybody is urging for getting more and more code covered with Javadoc and internal code documentation. Actually there was a couple of files and whole packages commited with *no* javadoc at all or even without licenses headers.

[jira] Updated: (DIRMINA-601) Add sendfile support to transport-apr

2008-06-11 Thread Geoff Cadien (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoff Cadien updated DIRMINA-601: - Attachment: (was: sendfile-patches.zip) > Add sendfile support to transport-apr > --

[jira] Updated: (DIRMINA-601) Add sendfile support to transport-apr

2008-06-11 Thread Geoff Cadien (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Geoff Cadien updated DIRMINA-601: - Attachment: sendfile-patches.zip Added patch for NioProcessor to use SendableFile > Add sendfil

Javadoc & commits

2008-06-11 Thread jvermillard
Hi, If you are following the commit log, everybody is urging for getting more and more code covered with Javadoc and internal code documentation. Actually there was a couple of files and whole packages commited with *no* javadoc at all or even without licenses headers. We are far of discussing a

Re: Current state of 2.0

2008-06-11 Thread Emmanuel Lecharny
Alex Karasulu wrote: +1 with pushing in all the API changes we will need for a long long time to come. Make the users happy. That means taking a little longer with 2.0 GA but probably not that much longer and we're close as Nicklas says. Let's go for all the good stuff as discussed in the BB t

Re: Current state of 2.0

2008-06-11 Thread Alex Karasulu
+1 with pushing in all the API changes we will need for a long long time to come. Make the users happy. That means taking a little longer with 2.0 GA but probably not that much longer and we're close as Nicklas says. Let's go for all the good stuff as discussed in the BB threads and get this wra

Re: Current state of 2.0

2008-06-11 Thread Niklas Gustavsson
On Wed, Jun 11, 2008 at 8:59 PM, Brian McCallister <[EMAIL PROTECTED]> wrote: > Get the 2.0 API to the one you want to use for the next five years and then > use it for the next five years. I agree, and for me we are there already. /niklas

Re: Current state of 2.0

2008-06-11 Thread Brian McCallister
On Wed, Jun 11, 2008 at 10:37 AM, peter royal <[EMAIL PROTECTED]> wrote: > On Jun 11, 2008, at 10:26 AM, Brian McCallister wrote: > >> Frequent (one a year is very very frequent) backwards incompatible API >> changes lead to no users. If ya'll take this roadmap I, for one, will go >> find some lib

[jira] Commented: (DIRMINA-601) Add sendfile support to transport-apr

2008-06-11 Thread Geoff Cadien (JIRA)
[ https://issues.apache.org/jira/browse/DIRMINA-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604282#action_12604282 ] Geoff Cadien commented on DIRMINA-601: -- Mike, You are correct that the ability to re

Re: Current state of 2.0

2008-06-11 Thread peter royal
On Jun 11, 2008, at 10:26 AM, Brian McCallister wrote: Frequent (one a year is very very frequent) backwards incompatible API changes lead to no users. If ya'll take this roadmap I, for one, will go find some library which isn't going to dead end me in the *foreseeable* future. agreed 100%

Re: Current state of 2.0

2008-06-11 Thread Emmanuel Lecharny
Brian McCallister wrote: Frequent (one a year is very very frequent) backwards incompatible API changes lead to no users. If ya'll take this roadmap I, for one, will go find some library which isn't going to dead end me in the *foreseeable* future. This is something we have to consider, that

Re: Current state of 2.0

2008-06-11 Thread Brian McCallister
Frequent (one a year is very very frequent) backwards incompatible API changes lead to no users. If ya'll take this roadmap I, for one, will go find some library which isn't going to dead end me in the *foreseeable* future. -Brian On Wed, Jun 11, 2008 at 10:09 AM, Emmanuel Lecharny <[EMAIL PROTEC

Re: Current state of 2.0

2008-06-11 Thread Emmanuel Lecharny
peter royal wrote: On Jun 11, 2008, at 9:07 AM, Emmanuel Lecharny wrote: we have discussed both options a month ago, and there were quite a concensus to get these changes into a postponed 2.0, instead of delivering a 2.0 and including changes into a 3.0. Now the environment has changed a bit

Re: Current state of 2.0

2008-06-11 Thread peter royal
On Jun 11, 2008, at 9:07 AM, Emmanuel Lecharny wrote: we have discussed both options a month ago, and there were quite a concensus to get these changes into a postponed 2.0, instead of delivering a 2.0 and including changes into a 3.0. Now the environment has changed a bit in the last few we

Re: Current state of 2.0

2008-06-11 Thread Emmanuel Lecharny
peter royal wrote: On Jun 6, 2008, at 8:31 AM, Craig L. Ching wrote: Yeah, I'm just wondering if there have been any commits yet that have fundamentally changed the API's (ByteBuffer in particular) that might "get" me if you know what I mean. I'm fine with the changes I'm hearing, don't get m

Re: Current state of 2.0

2008-06-11 Thread Niklas Gustavsson
On Wed, Jun 11, 2008 at 5:43 PM, peter royal <[EMAIL PROTECTED]> wrote: > On Jun 6, 2008, at 8:31 AM, Craig L. Ching wrote: > The fundamental changes to the IoBuffer API very likely won't happen for > 2.0, since 2.0 is close to being complete. > > At this stage, I think the best approach will be fo

Re: Web site refactoring proposal

2008-06-11 Thread peter royal
On Jun 7, 2008, at 6:24 AM, Emmanuel Lecharny wrote: IMHO, it would make things much easier to find for users and contributors. Last, not least, we might want to add some pointers to the AsycWeb and FTPServer subprojects, for instance on the top right menu (cf what we have on http://direct

Re: Current state of 2.0

2008-06-11 Thread peter royal
On Jun 6, 2008, at 8:31 AM, Craig L. Ching wrote: Yeah, I'm just wondering if there have been any commits yet that have fundamentally changed the API's (ByteBuffer in particular) that might "get" me if you know what I mean. I'm fine with the changes I'm hearing, don't get me wrong, I'm just

Re: IoProcessor stop creating new thread of IoHandler?

2008-06-11 Thread peter royal
On Jun 5, 2008, at 11:02 AM, Johny Kadarisman wrote: In my client implementation, I set manual threading model, and insert executorFilter() in my socketConnector config. On certain condition, in my handler, I will block in 'ArrayBlockingQueue'. during this situation, I don't see IoProcessor c

Re: AW: multiple ProtocolCodecFilters with MINA 2.0

2008-06-11 Thread peter royal
On Jun 2, 2008, at 9:24 AM, Thomas Kistel wrote: Sorry for cross-posting, but I haven't hidden that in my email. So there will be no ability for using multiple ProtocolCodecFilters in MINA 2.0 as Trustin Lee prefigured last year!? I believe it should "just work" in 2.0. Give it a shot and l

Re: How to properly synchronize external code with MINA

2008-06-11 Thread peter royal
On May 27, 2008, at 3:27 PM, Yigal Rachman wrote: I asked about this in February and have managed to move ahead without a proper solution. However, I am seeing glitches that point to synchronizing problems, so I would greatly appreciate any help that you could offer me. To recap: how do I

FtpServer milestone plan

2008-06-11 Thread Niklas Gustavsson
Hi I would like us to start discussing to road to a first 1.0 release of FtpServer. Here's my view at how I would like to organize our remaining work, feel free to provide input about timing or stuff you would like to include or exclude. Note that this list start with the M2 milestone, we actually

Clarification of the rumors around MINA and me

2008-06-11 Thread Trustin Lee
Hello, A few members asked me clarify the rumors around MINA and me, and here's my answers to some questions I received. http://blog.gleamynode.net/2008/06/clarification-of-rumors-around-mina-and.html -- Trustin Lee - Principal Software Engineer, JBoss, Red Hat -- what we call human nature i