Android – i-jetty or jetty

I have a web application hosted on an Android device. I am currently using the simulator provided by Android SDK. My application will provide both static and dynamic data. I am currently using jetty version 6.1.22. I want to ask what is a better choice. 1. Jetty web server with stripped code. 2. I-jetty

My application uses the following features –

>Resourcehandler provides static resources. > General servlet used to provide synchronous data requests. > extension of cometservlet used to provide asynchronous data requests

I look forward to following comparative standards

>Application size. The size of APK will include code. > memory and CPU utilization, and the maximum load is 30 requests / s. These are short bursts, which rarely occur in the application life cycle. The average load is about 5 requests / s. > easy to maintain. Including jetty's important upgrade in the application. > any other side effects I may miss

resolvent:

I've also been looking for information about embedding the i-jetty server in the application. Like the original poster, I need to provide static and dynamic resources. I found the following post a useful start:

http://puregeekjoy.blogspot.com/2011/06/running-embedded-jetty-in-android-app.html

I noticed that when searching for answers about embedding web servers in Android applications, many respondents did not provide useful answers, so if you want to do such a thing in "mobile phone", you have to laugh at the original poster. Then they continue to give all the reasons for not doing so. Except mobile phones, There are more Android devices. My project involves such a device. Thank you and I for guiding all useful answers on my other websites. I hope the links I provide can help other searchers