On Thu, Apr 24, 2008 at 12:43 PM, Julien Vermillard
<[EMAIL PROTECTED]> wrote:
> > I will -1 any new release until this is done, or at least, in a good
> > progress state, FYI.
>
> Well is it reasonable to block milestone for doc issues ? blocking dot
> zero release or RC I understand, but M i
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592171#action_12592171
]
Emmanuel Lecharny commented on DIRMINA-379:
---
Tanks guys !
Seems that we are pro
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592152#action_12592152
]
vcdaniel edited comment on DIRMINA-379 at 4/24/08 12:11 PM:
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592152#action_12592152
]
Daniel Wirtz commented on DIRMINA-379:
--
For 2.0.0-M1 the fix is:
Change
private
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592149#action_12592149
]
Stefano Bagnara commented on DIRMINA-379:
-
My patch above didn't fix the issue.
N
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592132#action_12592132
]
Stefano Bagnara commented on DIRMINA-379:
-
I checked out the latest 1.1 branch (1.
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592104#action_12592104
]
vcdaniel edited comment on DIRMINA-379 at 4/24/08 9:05 AM:
---
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592104#action_12592104
]
Daniel Wirtz commented on DIRMINA-379:
--
Yes, I think this could be the reason. I trie
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592097#action_12592097
]
Emmanuel Lecharny commented on DIRMINA-379:
---
May it be connected to this descrip
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara reopened DIRMINA-379:
-
Updated to jdk6 update 6 and now I see it more rarely, but after some run I saw
the same ex
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592088#action_12592088
]
Daniel Wirtz commented on DIRMINA-379:
--
Fully updated Windows Vista, JRE 1.6.0_06 and
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592065#action_12592065
]
Daniel Wirtz commented on DIRMINA-379:
--
I can confirm this bug under Windows Vista wi
"이희승 (Trustin Lee) <[EMAIL PROTECTED]>" wrote:
Emmanuel Lecharny wrote:
I have also some concerns about some classes which should have been
removed or deprecated. There where a convo two years ao about pooled
ByteBuffer, where we stated that it was dubious, and can be removed. I
see no reason
Emmanuel Lecharny wrote:
> I have also some concerns about some classes which should have been
> removed or deprecated. There where a convo two years ao about pooled
> ByteBuffer, where we stated that it was dubious, and can be removed. I
> see no reason to keep those pooled BB into the 2.0 code ba
David M. Lloyd wrote:
On 04/24/2008 05:06 AM, Emmanuel Lecharny wrote:
Hi,
I have created DIRMINA-575, set to blocker. We need better
documentation, otherwise we won't be able to get new committers to
get into the code base.
I will -1 any new release until this is done, or at least, in a go
On 04/24/2008 05:06 AM, Emmanuel Lecharny wrote:
Hi,
I have created DIRMINA-575, set to blocker. We need better
documentation, otherwise we won't be able to get new committers to get
into the code base.
I will -1 any new release until this is done, or at least, in a good
progress state, FYI
Julien Vermillard wrote:
Hi,
On Thu, 24 Apr 2008 12:06:57 +0200
Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
Hi,
I have created DIRMINA-575, set to blocker. We need better
documentation, otherwise we won't be able to get new committers to
get into the code base.
It's not just commi
Hi,
On Thu, 24 Apr 2008 12:06:57 +0200
Emmanuel Lecharny <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have created DIRMINA-575, set to blocker. We need better
> documentation, otherwise we won't be able to get new committers to
> get into the code base.
It's not just committers, it's for users too, t
Hi,
I have created DIRMINA-575, set to blocker. We need better
documentation, otherwise we won't be able to get new committers to get
into the code base.
I will -1 any new release until this is done, or at least, in a good
progress state, FYI.
I have also some concerns about some classes w
Add the missing Javadoc, add some comments
--
Key: DIRMINA-575
URL: https://issues.apache.org/jira/browse/DIRMINA-575
Project: MINA
Issue Type: Improvement
Affects Versions: 2.0.0-M2, 1.0.11, 1.1.8
[
https://issues.apache.org/jira/browse/ASYNCWEB-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591962#action_12591962
]
Julien Vermillard commented on ASYNCWEB-11:
---
heh I'm idiot the endless loop is m
Hi Trustin,
Sounds great !!!
Maarten
On Thu, Apr 24, 2008 at 10:44 AM, "이희승 (Trustin Lee) <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> There are currently 47 unresolved issues in our issue tracking system.
> IMO, they can be categorized into the following categories:
>
> 1) Bugs that needs fix
>
> http
Hi,
There are currently 47 unresolved issues in our issue tracking system.
IMO, they can be categorized into the following categories:
1) Bugs that needs fix
https://issues.apache.org/jira/browse/DIRMINA-539
https://issues.apache.org/jira/browse/DIRMINA-574
These are known bugs so they need to
[
https://issues.apache.org/jira/browse/DIRMINA-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trustin Lee resolved DIRMINA-379.
-
Resolution: Cannot Reproduce
Assignee: Trustin Lee
Can't reproduce in my Windows Vista. P
[
https://issues.apache.org/jira/browse/DIRMINA-573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trustin Lee resolved DIRMINA-573.
-
Resolution: Invalid
Assignee: Trustin Lee
Seems like my example has resolved your concern.
[
https://issues.apache.org/jira/browse/DIRMINA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trustin Lee resolved DIRMINA-25.
Resolution: Fixed
Fix Version/s: 2.0.0-M2
This issue has been resolved. Please refer to the
[
https://issues.apache.org/jira/browse/DIRMINA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trustin Lee reassigned DIRMINA-25:
--
Assignee: Trustin Lee
> Overload prevention
> ---
>
> Key: DIRM
If one to one conection, non blocking is NOT better than blocking io. NIO is
better used as a server which needs to serve thousands of clients.
On Thu, Apr 24, 2008 at 12:41 AM, Michael Qi <[EMAIL PROTECTED]> wrote:
> Hi steve,
>Thank you for your reply.
>I see someone used ten or more co
[
https://issues.apache.org/jira/browse/ASYNCWEB-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12591943#action_12591943
]
Julien Vermillard commented on ASYNCWEB-11:
---
I tried decoding this response, It'
29 matches
Mail list logo
