Guten Tag Sven Meier, am Samstag, 20. Juni 2015 um 20:18 schrieben Sie: > there seem to be different solutions already, why do you think they are > not promising?
> https://github.com/jetty-project/i-jetty The commit history doesn't look very active to me and I've read that Tomcat and newer versions of Jetty rely on JMX, which shall be a no go on Android. On SO where some unanswered questions about Tomcat on Android as well. But I'm just at the start of my research and didn't try anything myself yet. > Actually it would be interesting to just skip all servlet stuff and just > use an HTTP server: > https://github.com/NanoHttpd/nanohttpd And why would that be interesting or preferable or whatever? Besides the fact that it might be the only working solution at all, of course. ;-) I guess it might be faster and such, but would mean that the frontend needs adoption for both different environments, executing within a servlet container or not. That's exactly what I would like to avoid as much as possible. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org