Ta daaaaa! Drum roll please.
We are pleased to announce that the first release of i-jetty is available. i-jetty is a port of Jetty to the Google Android phone. This release works with the most recent release – SDK 1.0r1 – of the Android platform.
Go to http://code.google.com/p/i-jetty/ and follow the links to download it now.
i-jetty not only puts a Jetty webserver on your Android phone, but it also comes with some sample webapps that you can access from the phone AND from your desktop browser – indeed any browser that is on a network accessible to the phone.
The sample webapps are:
- hello
- A simple webapp with a static page leading to a HelloWorld servlet.
- chat
- A chatroom webapp that uses Cometd to do an Ajax chatroom.
- console
- A webapp that allows you to access and manipulate the on-phone information such as Contacts, Settings, Call logs etc via a browser. No more sync’ing of on-phone data with your pc in order to get that person’s email address any more – email them direct from your desktop browser!
As you might have read on Greg’s blog, it hasn’t been easy developing for Android due to the restricted access to timely bug fixes, sketchy documentation and of course the lack of access to the source code.
However, on the positive side, the dalvik vm does support many of the java libraries used by Jetty, and Jetty itself of course has a long history of excellent embeddability on all kinds of devices.
Oh, and we’re pining for one of those oh-so-cool Android handsets so if someone was so kind as to send one our way, we’d be disgustingly grateful 🙂
5 Comments
Alex Hixon · 10/10/2008 at 08:55
Yehaw! 🙂
Awesome work Jan.
Josef Holland · 28/10/2008 at 18:48
i Jetty does not appear to be working, Well it does from the G1 useing local loop back 127.0.0.1 but cannot connect via the net Beleive it’s the ip address that i’m given the phone gives me my rmnet0 ip address then going to whats my ip gives me another ip address. I tried connecting via both from my home comp through the net to no avail… and i did try alternative ports in case T-Mobile blocked access to 8080.
Please let me know if you have a solution.
Jan Bartel · 28/10/2008 at 22:13
Hi Josef,
Lucky you to have a real Google phone! As the phones aren’t available in Australia yet I haven’t got one, so I haven’t been able to test this out for myself. A colleague in the USA tried it for me and reported the same issue as you. I’ll ask you to do the same thing I asked him to do, and that is, to try and use it via the wireless to your local LAN. I would expect that to work – does it? Possibly TMobile is blocking inbound gprs-based connections to the phone.
I’m not sure why the other IP addresses aren’t working. Jetty should be listening on port 8080 on all known interfaces.
Is there a log you can look at? There is with the emulator but I’m not sure what is provided on a real phone.
regards
Jan
Josef Holland · 30/10/2008 at 19:30
I have no LAN setup at home but will try and let you know.
But it appears that tmobile is the problem because the ip of the phone is different then what the net sees.
Because the app tells us rmnet ip is one thing
Then the site whatsmyip.com says the ip is different.
Its like a computer on a network the router gives you an ip but uses it’s own ip for accessing sites and the sites never see the ip that the router assigned to you only the routers.
It’s good that you have to wait inAUS because they are working out minor bugs. But you will love it, at least I know I do.
Josef Holland · 30/10/2008 at 19:32
Ps sorry, no log to my knowledge.
Comments are closed.