For me, Tomcat is just an example of a complete implementation. For
our application we just need HTTP, HTTPS, and some basic server
instrumentation and logging to identify problems.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to
Hi,
Saw this as well -
http://www.androidzoom.com/android_applications/communication/kws-android-web-server_hlfb.html
Implementing a simple / custom webserver / appserver is pretty
straight forward, don't understand why you'd need Tomcat (java
servlet) capabilities ?
Regards
On Nov 6, 3:17
My experience is that Jetty (http://www.mortbay.org/jetty/) tends to
be a bit more lightweight than tomcat, and also a LOT easier to embed
(it's basically just a JAR file).
Or you could try this:
http://tjws.sourceforge.net/
Haven't tried it myself, but looks like it's designed to be
I guess if it's a wall
mounted device, it might be ok. But at that point why not just use a
PC of sorts and use some linux distribution and use your app as is,
why even use Android at all?
You would be surprised how difficult it is to get a decent ARM based
fanless PC with a stable linux and
Thanks Jason. Very useful. i-jetty looks quite interesting run as a
service on android and may just be the ticket.
I may also contact the tjws guy see if he is porting to android.
On A/ this is meant for an in-wall device so no issues of power.
Thanks again.
MF
On Nov 5, 7:20 am, Jason
Hello Marc and Bret
would be nice, if you could describe what you try to do ?!
Currently the easiest thing for you would be i-jetty,
the android port of jetty from WebTide
Look here : http://code.google.com/p/i-jetty/
And after that provide your impressions to the community.
Thanks !
What we need is something with built-in 3G and WiFi, a small touch-
screen, low power consumption, fan-less, and able to tolerate frequent
power cycling. It should also have a large installed base (millions),
lots of developers familiar with it, and the hardware should be
available from a number
Also, an integrated database designed to run on top of NV memory would
be helpful.
On Nov 5, 8:53 am, Bret Foreman bret.fore...@gmail.com wrote:
What we need is something with built-in 3G and WiFi, a small touch-
screen, low power consumption, fan-less, and able to tolerate frequent
power
I'm afraid I agree with the previous postings. This looks difficult
under Android Java, you
may be better off by creating you own component server.
I would recommend a server based on MDP messaging and sockets:
MDP and a distributed Component/Service Model
I've been looking into this too. We have an industrial embedded
control application that I'd like to run on Android and control from a
remote browser.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
All I gotta ask is, why? I'd imagine Tomcat is not written to be run
in embedded/legacy devices such as an android device. You'd be
wasting a lot of memory and cpu cycles. I guess if it's a wall
mounted device, it might be ok. But at that point why not just use a
PC of sorts and use some linux
11 matches
Mail list logo
