Hi!
Sajit Zachariah wrote:
MINA is used for writing the client which connects to a device on tcp/ip.
After establishing the connection with the device, If the network cable is
unplugged of the device/client is unplugged, I was expecting a
sessionclosed invocation but it is not happening.
Julien Vermillard wrote:
I made a little filter for generate random garbage in your byte streams.
Hi!
Thanks, looks very nice. Just startet a test, and found a bug in my app at
the first try. :-)
The output of the changed bytes is very useful, you just have check for
0-values, because
semi wrote:
Hi, I would like to know if there are some way to get total bytes recived
including TCP protocol bytes (Head TCP-IP, CRC..., and all datagram
retrasmition). I am studying about use Jpcap but is a difficult solution.
All control methods to integrate MINA with JMX are usuless.
Michael Bauroth wrote:
is there a special reason, why the NioSocketConnector hasn't the same
methods like the acceptors (bind, unbind, isBound vs. connect,
disconnect, isConnected)? Would be fine if somebody could bring some
more light into this :)
Hi!
I think that's because the
jgenender wrote:
Hey guys,
I was hoping to see if we could discuss some of the final qualifiers
on some of the methods in the AbstractIOSession. The reason I ask is it
would be cool to be able to override some of the methods such as:
public WriteFuture write(Object message)
public
Steve Johns-2 wrote:
Did everyone test if Mina drops the message under heavy loading? In Mina
wesite, I only saw the HTTP server benchmark test. Does everyone have the
pure socket server benchmark test result? Thanks in advance.
Hi!
I can't agree to this. But there are some reasons why
Emmanuel Lecharny-3 wrote:
While looking at the abstract class, I found some methods with this kind
of code :
public final WriteFuture write(Object message, SocketAddress
remoteAddress) {
if (message == null) {
throw new NullPointerException(message);
Hi!
we're using mina 2.x too and it is very stable. API changes from time to
time slightly, but most of this changes are cosmetic changes to harmonize
and clear out the API, so there's no need redesign your application, just a
bit cleanup or refactoring (which should be done regulary, though).
Hi Trustin
Trustin Lee wrote:
I thought about this issue again and again every night (OK, I'm
exaggerating) and realized what you want to do (overriding
AbstractIoSession.write()) can be done alternatively by adding a
filter that intercepts the write call. Does it fulfill your needs?
Hi Mina-folks,
we're using the trunk/2.0 version of mina in some of our apps.
For test purposes I used a DummySession and mocked the write() and
close()-methods with easyMock classextension, because I'm not interested in
any other method calls, like get/setAttribute. Some of these Methods are
10 matches
Mail list logo