MINA and "Java EE" are not really comparable. MINA is a relatively low
level networking library whereas "Java EE" is a collection of higher level
APIs for doing a variety of things including web applications, persistence
and RPC. Some of those may involve HTTP but not all of them - for example
HTTP is irrelevant for EJB persistence.
What does your application do?
If you would consider writing your application using sockets then MINA
definitely is worth looking at. If you would consider writing your
application using RMI or CORBA then "Java EE" may be a more appropriate
choice. It depends on how close to the wire you need to get.
Robert
"David Fire"
<[EMAIL PROTECTED] To:
[email protected]
ail.com> cc:
Subject: Re: TCP server
09/03/2006 19:57
Please respond to
mina-dev
Thanks.
Is my observation about Java EE correct, in that it is HTTP-oreiented?
>From: peter royal <[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: TCP server
>Date: Thu, 9 Mar 2006 14:05:12 -0500
>
>On Mar 9, 2006, at 1:54 PM, David Fire wrote:
>>I'm new to MINA, and hence the newbie question.
>>I need to develop a server that serves (mobile) clients via a TCP
>>connection. Clients may maintain a connection open for various periods
of
>>time (depending mainly on network coverage).
>>Is MINA the right framework for me? Is there anything in Java EE that
can
>>also do this (I'm just taking my first steps with that also), or is it
>>solely HTTP-oriented?
>
>You could certainly do that with MINA.. in fact mina would be ideal if
you
>have lots of longer-lived connections, since it would be able to scale
>nicely.
>-pete
>
>--
>[EMAIL PROTECTED] - http://fotap.org/~osi
>
>
><< smime.p7s >>
This communication is for informational purposes only. It is not intended
as an offer or solicitation for the purchase or sale of any financial
instrument or as an official confirmation of any transaction. All market prices,
data and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.
