On Dec 17, 2007 12:31 PM, Trustin Lee [EMAIL PROTECTED] wrote:
On Dec 14, 2007 7:56 AM, Steve Johns [EMAIL PROTECTED] wrote:
On Dec 14, 2007 6:40 AM, mat [EMAIL PROTECTED] wrote:
On Dec 14, 2007 1:35 AM, Trustin Lee [EMAIL PROTECTED] wrote:
Hi Steve,
On Dec 13, 2007
Welcome Jeff !
On Fri, 14 Dec 2007 16:29:50 -0500
Alex Karasulu [EMAIL PROTECTED] wrote:
Hi all,
We have a new committer, Jeff Genender, who's a committer other
projects here at the ASF and a member of the foundation as well.
He's great guy and has been working on some of the http client
Welcome Jeff !
Maarten
On Dec 17, 2007 9:32 AM, Julien Vermillard [EMAIL PROTECTED] wrote:
Welcome Jeff !
On Fri, 14 Dec 2007 16:29:50 -0500
Alex Karasulu [EMAIL PROTECTED] wrote:
Hi all,
We have a new committer, Jeff Genender, who's a committer other
projects here at the ASF and
[
https://issues.apache.org/jira/browse/DIRMINA-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David M. Lloyd closed DIRMINA-497.
--
Resolution: Invalid
Ah yes, you are correct - I looked a while back and noticed that there is
[
https://issues.apache.org/jira/browse/DIRMINA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552402
]
David M. Lloyd commented on DIRMINA-495:
The name is unimportant to me - Mike?
IoConnector needs a way to
Hello all,
On Dec 17, 2007 6:25 AM, Trustin Lee [EMAIL PROTECTED] wrote:
Hi Maarten,
On Dec 15, 2007 3:26 AM, Maarten Bosteels [EMAIL PROTECTED] wrote:
about (4) : I thought the deadlock is caused by a bug in log4j (namely that
it doesn't use proper synchronization) ?
If that's the case
On Mon, 17 Dec 2007 17:29:24 +0100 Maarten Bosteels
[EMAIL PROTECTED] wrote:
I agree, there are currently two logging facades that are widely used
by frameworks/libraries: jakarta-commons-logging (JCL) and SLF4J.
The consequence is that for any project with dependencies, there is a
reasonable
Hi,
I've found a problem in the HTTP codec because some server incorrectly
send the chunk length.
These servers send the length follwed by some spaces, before the CRLF
terminator.
Example: http://del.icio.us/
The following patch fixed the problem for me:
Index:
David M. Lloyd wrote:
How would you feel about things if MINA required slf4j AND jcl AND
log4j? That would seem excessive, would it not? It might even affect
one's willingness to use the framework.
This is the situation that I (and others with whom I work) face
currently. As a framework
Trustin Lee wrote:
snip/
However, taking
the item #4 into picture, it leads me to think we need a thin built-in
layer for logging that is dedicated to MINA.
Please, don't ! This is MINA, a Network framework, not a Logger
framework ! We already have so many meta-meta-meta-loger around
On Dec 17, 2007 11:29 AM, Maarten Bosteels [EMAIL PROTECTED] wrote:
On Dec 17, 2007 6:25 AM, Trustin Lee [EMAIL PROTECTED] wrote:
...
We can ask Log4J team to fix this issue and it will be fixed, but,
again, considering that people wants to use the older version of Log4J
or doesn't want
Hi David,
On Dec 17, 2007 5:46 PM, David M. Lloyd [EMAIL PROTECTED] wrote:
On Mon, 17 Dec 2007 17:29:24 +0100 Maarten Bosteels
[EMAIL PROTECTED] wrote:
I agree, there are currently two logging facades that are widely used
by frameworks/libraries: jakarta-commons-logging (JCL) and SLF4J.
Hi Trustin,
We could make our current class hierarchy more granular like the following:
* HttpMessage
** HttpRequest - no getContent()
*** MergedHttpRequest - getContent() here
*** ChunkedHttpRequest - once written, encoder expects HttpChunks,
other HttpRequest or disconnection.
**
On Mon, 17 Dec 2007 20:11:20 +0100
Maarten Bosteels [EMAIL PROTECTED] wrote:
Hi David,
Some people have feelings stronger than preference about it. Also keep
in mind: you've got an application. You are not developing a framework.
How would you feel about things if MINA required slf4j
I think you've got the list.
I would suggest you to look at some mails I wrote under subject
http://www.nabble.com/-jira--Created-3A--28DIRMINA-477-29-Update-page-about-differences-between-1.x-and-2.x-to13740995s16868.html
specially those using Update page about differences between 1.x and 2.x as
Hi Trustin,
I double check and I don't see why I still have 0 value
for ReadMessages and ReadMessagesThroughput in IoHandler,
while ReadBytes and ReadBytesThroughput are non zero
in the same time.
I have written an extension in my business logic to count
myself current Messages each 3 seconds
Hi Alex,
In reference to the MINA-based appender re-entrance problem as described in
http://xrl.us/bctaa , I would suggest that logging from the I/O processor
thread be disabled.
As for JBoss, did you know that Hibernate 3.0, the next version of Hibernate,
relies on SLF4J for its logging?
David M. Lloyd wrote:
My point is, as a framework, MINA should work to avoid imposing this
preference upon the consumer of the framework. That's just friendly
programming practice: make as few assumptions as possible about the
user's environment, and impose as few constraints as possible.
[
https://issues.apache.org/jira/browse/DIRMINA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Heath resolved DIRMINA-495.
Resolution: Fixed
I went with the name IoSessionInitializer for the callback interface. This
On Dec 18, 2007 3:34 AM, Emmanuel Lecharny [EMAIL PROTECTED] wrote:
Trustin Lee wrote:
snip/
However, taking
the item #4 into picture, it leads me to think we need a thin built-in
layer for logging that is dedicated to MINA.
Please, don't ! This is MINA, a Network framework, not a
On Dec 18, 2007 3:40 AM, Alex Karasulu [EMAIL PROTECTED] wrote:
On Dec 17, 2007 11:29 AM, Maarten Bosteels [EMAIL PROTECTED] wrote:
On Dec 17, 2007 6:25 AM, Trustin Lee [EMAIL PROTECTED] wrote:
...
We can ask Log4J team to fix this issue and it will be fixed, but,
again, considering that
Trustin,
If MINA uses it's own logging, and logs critical related messages on a
separate channel, then an application written with MINA yet using another
framework will channel log messages to potentially different targets.
Sometimes you just don't get the best of both worlds. There are trade
Hi Qi,
It's not a bug but a kind of dead lock caused by misuse of the API.
You are usually not supposed to call IoFuture.join() within an
IoHandler because the IoHandler methods might be being executed in the
same thread with the I/O processor thread. You wrote something and
you call join() to
On Dec 17, 2007 5:20 PM, Steve Johns [EMAIL PROTECTED] wrote:
snip/
Can you give more hints about what the CACHE is?
In you encoder, you could maintain a Map whose key is some message key
and whose value is encoded ByteBuffer (or byte[]). It could probably
be a LRUMap implementation
On Dec 18, 2007 3:15 PM, Trustin Lee [EMAIL PROTECTED] wrote:
On Dec 17, 2007 5:20 PM, Steve Johns [EMAIL PROTECTED] wrote:
snip/
Can you give more hints about what the CACHE is?
In you encoder, you could maintain a Map whose key is some message key
and whose value is encoded
25 matches
Mail list logo
