directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jose Alberto Fernandez" <>
Subject [mina] Using StreamIoHandler
Date Fri, 14 Oct 2005 10:29:47 GMT
Hi guys,


We are starting to explore how to use MINA and as a first step we would
like to try a simple telnet like interface into the server.

As the protocol with the client has not been completely defined yet, we
would like to start with some line based commands to test what we are


Are there any examples on how to code usage of StreamIoHandler? The API
says one needs to forward the request to a separate thread or
thread-pool, does anyone has examples of how to use the thread pools for
this purpose? 


Any hints are appreciated and thanks for the good work.


Jose Alberto



From: Trustin Lee [] 
Sent: 14 October 2005 04:39
To: Apache Directory Developers List
Subject: [mina] TLS protocol closure and MINA versioning strategy.



Now we are able to implement StartTLS, but what about TLS closure
(reverting back to non-encrypted mode)?

I've found that MINA filters cannot filter session close requests so
that SSLFilter send close_notify.  We also don't have any way to notify
the removal of SSLFilter from session-scope filter chain to SSLFilter
itself so that it can send close_notify to revert back to non-encrypted
mode without closing the connection in MINA 0.7.  Fortunately we've got
filterAdded and filterRemoved in trunk (0.9 stream).

I think porting back these features and adding filterClose() to filters
in 0.7 stream just increases my maintenance overhead.  I'd like to
change current linux-like versioning scheme of MINA to just plain one;
to release current branch as 0.7.5 and trunk as 0.8 soon with full
StartTLS and TLS closure support.  I don't see any good reason to retain
current versioning scheme in current situation.


what we call human nature is actually human habit 

View raw message