Yeah I am in agreement with Mike. An architectural overview...and an
example (heck use AHC vs HttpClient) and show how it scales. That will
get ooohs and ahhhs.
Jeff
Mike Heath wrote:
One of the problems I've had when promoting MINA is that most Java
developers don't understand the
One of the problems I've had when promoting MINA is that most Java
developers don't understand the scalability implications of the
thread-per-connection architecture. If I jump right in with how cool
MINA is with its separation of concerns, futures, filters, event
mechanism, simplifies packet
I think it would be also interesting to discuss the higher-level
appeal of MINA. For anyone not familiar with it at the talk, I think
the amazing thing about MINA is how easily you can create really
robust, high performance clients and servers for any protocol
extremely quickly -- the advantages
Jeff Genender wrote:
Yeah I am in agreement with Mike. An architectural overview...and an
example (heck use AHC vs HttpClient) and show how it scales. That will
get ooohs and ahhhs.
Jeff
+1, using a protocol that a lot of developers people are actually
familiar with would help a lot.
-Mike
Hi,
I was invited as a speaker of JavaOne 2008 and will speak about Apache
MINA there. Please feel free to contact me to give me some idea about
what you want to hear about MINA if you have any plan to attend this
year's JavaOne.
Cheers,
Trustin
--
what we call human nature is actually human