Hi Trustin,
Like i already replied myself,
synchronizing on IoSession.write did the job.
Unfortunately i can not open source the
code ;-( (company decision), but like i described
it is any rmi-like framework with extended
functionality like oneway messages, callbacks,
multiple targets in a singl
I sent the following email to [EMAIL PROTECTED]
James Im wrote:
In the MINA mailing list came up a question that I believe the API must
answer.
We need a way to query the system about the available native API. We
need to know if we will get better performance with the asynchronous API
or non-bl
On 5/23/07, Johan Cloetens <[EMAIL PROTECTED]> wrote:
Hi Trustin,
Like i already replied myself,
synchronizing on IoSession.write did the job.
I meant it must work without any manual sychronization unless it's
related with your business logic or codec.
Unfortunately i can not open source the
could you send me your code? My first guess is that you don't have your JMX
bean set up properly and/or registered.
On 5/22/07, Eero Nevalainen <[EMAIL PROTECTED]> wrote:
I'm using JDK 5. I gave the argument
-Dcom.sun.management.jmxremote
to the "VM arguments" list under "Run as"->"Run"->"Arg
[
https://issues.apache.org/jira/browse/DIRMINA-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12498196
]
Mladen Turk commented on DIRMINA-382:
-
Why not add shutdown() instead parameterized close.
It would also allow a
did you mean to put something in this email
On 5/23/07, Brigham Stevens <[EMAIL PROTECTED]> wrote:
--
..Cheers
Mark
I'm running version 0.9.3 and the session.close() actually does not seem
to end the session immediately. We're using session.close() for idle
timeouts, and it works great for well-behaved clients. However, for
clients who don't read the server responses and thus for whom mina is
queuing up write da
Hi Trustin,
Thanks for getting back to me. I know how busy one can get with e-mail on a
popular project. I appreciate your efforts to get back to everyone, even if it
takes some time. It is one of the things that will continue to grow the Mina
community.
Sorry the reply isn't quoted. Yahoo
(sorry for the blank message I put To: field to early and somehow bashed my
keyboard badly)
We were having problems with our mina client & server's UDP sessions.
They were being terminated by the ExpiringMap which is part of the
ExpiringSessionRecycler that is used for UDP sessions.
We didn't want
Hi,
I found some think they are the same. Do you know the difference?
Cheers,
Dong
--
Dong Liu
http://blogs.usask.ca/dong_notes/
Dong Liu wrote:
Hi,
I found some think they are the same. Do you know the difference?
With nio you call select and act accordingly to the returned values,
with async you register event handlers, and do that for multiple
files/sockets. Its something MINA already does internally.
Think I've be
Hi all,
I have an application which reuses IoSessions often. Basically as the
client sends data, state is built up within the IoSession via a
series of attributes. When the server recognizes that an event has
taken place, it processes the session, and clears the attributes for
the next ro
Hi,
I apologize for nagging but could someone please confirm or not if this is
happening to other people?
I've tried it on another computer at work and it can be reproduced always.
Regards,
Horia
seven wrote:
>
>
> Trustin Lee wrote:
>>
>> On 5/9/07, seven <[EMAIL PROTECTED]> wrote:
>>>
>>
Hey,
I'm using MINA 1.1 and tracking a problem where byte buffers stay in the
outgoing queue and are never flushed. So far the problem is hiding from
me. :( Not sure if that is also your case.
Any ideas on this issue?
Thanks,
-- Gato
-Original Message-
From: seven [mailto:[EMAIL PROT
I'm having some trouble creating a filter.
I need a filter that reads the content of the first received message
for authentication purposes. I'm trying to do something like the
EchoProtocolHandler does for reading the message:
ByteBuffer rb = ( ByteBuffer ) message;
// Write the re
So that means asynchronous I/O is what one can observe, and it can be
implemented or has already be implemented by NIO.
And I think NIO is also one of the approaches to implementing asynchronous
messaging or processing. I am not sure if I am right.
Please comment.
Cheers,
Dong
On 5/23/07, Mlad
Hi folks,
Is necessary disable the direct buffers on the 1.1.0 version??
I mean:
ByteBuffer.setUseDirectBuffers(false);
ByteBuffer.setAllocator(new SimpleByteBufferAllocator());
I was looking in the changes between version and I've not found anything about.
Another little question:
Is a good
AFAIK they are the same. Asynchronous and non-blocking are identical in
this context. They both mean that you don't have to wait for a response
to continue (as oposed to synchronous or blocking I/O). You need to work
with event handlers to process the responses (as mentioned by Mladen).
Check
On 23/05/2007, at 8:54 PM, Mladen Turk (JIRA) wrote:
Why not add shutdown() instead parameterized close.
It would also allow adding timeout (someting like lingering on
standard sockets)
Assuming MINA can't go back to close () having this behaviour (I
think most people would expect a close
19 matches
Mail list logo