Skip to main content

mobile web server

2 replies [Last post]
Joined: 2009-01-13
Points: 0


i am a student of Kuwait University ( Computer Engineering ) and i have senior project of making mobile web server with java (j2me) so would you please give the instructions and taps to create the mobile web server where my project will be similar to the new released product at (, please??

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2007-07-18
Points: 0

I think the most important question is, why do you want to recreate the MWS project in Java? Nokia have done it already with their Mobile Web Server / Raccoon project on Symbian. So redoing the same thing for your project isn't going to produce anything new.

But if you want to do it, you're going to have to get past the problem that Shawn pointed out about lack of DNS to a phone. Basically what you would have to do it create 2 parts to your system:

1) A mobile application that serves the web pages
2) A relay server that acts as the 'real' HTTP server on the Web.

Your mobile application makes a connection to the relay server (either direct or through periodic polling), then when the relay/real-Web server receives a request to a certain URL, the request is forwarded to the appropriate mobile phone and the mobile application responds with the data, which the relay then responds to the original HTTP request with that said data. Easy peezy.

You could use JXTA, but it might be easier to produce your own custom and lighter-weight solution if you're able to. Shawn's points about the value of doing this are quite right - and I've test-driven the Symbian MWS before - it works, but it's slow, unreliable, and very battery-hungry.

Joined: 2003-06-15
Points: 0

Let me start out by saying your goal of a webserver on the phone is (IMHO) a complete and total waste of time. The main reason is how are you going to point a desktop to a phone, or for that matter phone to phone. There is no DNS for phone that you, the average user or even sophisticated developer, can get to. I would imagine that this type of thinking is the very reason that Operators don't want to allow developers onto their networks.

Having said that the technologies you should look at and figure out how they work are OSGi, Jexta. OSGi can support the concept of a webserver on the phone, as well as the container concept which may be needed for loading and unloading webpage / apps / service.

Jexta gives you the ability to use a server and your DNS concept so the outside world can communicate with the mobile device. (I mean really do you understand how much storage space these devices have and the bloat of web pages built by tools. )

Some words of wisdom: Just because it can be done, doesn't mean it should be done. Albert Einstein regretted his involvement in recommending the US pursue Atomic weapons.
I hope in 5 years there is still a mobile market and that it is not running ramped with the ilk that has the web under siege today.