Hi Parki, On 11/8/07, parki <[EMAIL PROTECTED]> wrote: > > Hello! > > Hoping someone out there can help me out. > > I'm working on a project which entails a hardware device (which we are > building) talking HTTPS to a set of backend servers, and I'm trying to > determine the best choice for the server side - we'd like to run persistent > HTTPS connections and keep them alive, mainly to push data from the server > to the client (and vice versa) - we intend to run asynchronous > communications. We own both sides, and so it's a custom protocol, > keep-alive, and using HTTPS to get through firewall issues. > > So, a Servlet container (such as JBoss/Tomcat, which we are also using on > the web service side) is not going to work, as the Servlet container doesn't > allow for long running connections (the container is free to close the > connection on every response, and its not designed to host long running > threads). Therefore, looking around at alternatives. > > Mina looks very compelling, as I looks to fit the bill, but I have a couple > questions : > > 1. Given the description above, is Mina a good choice (loaded question :)
Yes. MINA was designed to be asynchronous from the day 0. > 2. Are there clustering issues? We will need to add hardware as needed (but > no need to share data between instances) so I'm assuming this will be a > non-issue, but want to raise it anyways. Not at all. > 3. Any other alternatives I should be looking at? There's HttpComponents project in the Apache Software foundation. I might provide a better out of the box support for HTTP. I'm not sure if it's asynchronous like MINA is though, but it will worth to take a look into. And we currently has a project called 'AsyncWeb' in our sandbox. There's working light weight web server example there, so you might want to take a look into there too. HTH, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
