Browser problems

There were some browser problems i.e direct RPC mysql is not possible because of a) sandboxing leading to Google's own connector with is only applicable for Premier editions which is paid. So we turn to http requests which don't work directly because of SOP same origin policy. So finally using a proxy servlet and RPC to talk using post we could communicate with the web server.

Well we could now complete the whole project in 5 days. Hopefully and then end it with documentation.

As for now browser -> web server-> database is done done done.

Database

This is really a new challenge we are facing. I at first informed you about database choices. I feel I would pragmatically decide to use MYSQL. Let us see how things turn up. Hopefully they would turn out to be better.

Can any one tell me tips and trick of servlet and MYSQL. How to work about it online.

Two problems

After speaking to

Prakash Sir we found out that a major part of the code that is server side code remained. Here there are various options like RPC, HTTP requests etc. But one important thing is that RPC is great and is inbuilt in default google project when we use eclipse. One can use flow player etc etc. But it should be compatible with the google app engine.

Another thing is about the android client is that what should we use XML RPC , JSON RPC or posts and gets. I would upload a complete helper for others on how I solved my problems. But for now I have chosen HTTP gets etc. For browser it would be RPC. Of course there is a discussion on XML vs JSON RPC and in case of android I find after goggling that XML RPC is meant for J2ME and you can go on with some technical changes required. in XML libraries. But on performance one should look at JSON if for RPC and preferably HTTP requests.

Others may disagree.

one important thing in my opinion is to make a cloud application which should not only include the browser but also include tablets smart phones and regular phone.To be precise most of the clients connecting the internet.

The problem to communicate with the server is solved as for now in case of both the android phone and the browser. I am happy for it. Hopefully I would be able to get things done regarding database and server connectivity. The above digram will illustrate the problem solved and unsolved.

Hope to show a good project in the coming competition.

I have to admit I haven't blogged for a long time but hopefully I would love to be regular.

After a long time

I am sorry that after a long time I have started to blog again. Well there were some placements going on so I was busy. As far as android is concerned one has to think. I have been able to work with listactivity and am now working on databases along with servlets. These two remain our greatest challenges.I have now put a self made deadline of 14th of Feb. I would expect to complete the whole thing by that time.

A great success

On the christmas day we had a big break thru. We were able to add a VLC player on web application using bst-player project on google code. Today i.e on the 27th of Dec were used inbuilt apache server on mac to progressively play music on both clients i.e. android emulator and web browser. Now I am thinking of extending it to iphone. Hopefully my dream may come true. Another idea that had cropped up is to add normal phone. This could be possible using SMS techniques.

Well I feel at this point a big part of our project is over.

SQL choices

We took 3 days off. We came to a decision for sql. We had choices such as MYSQL,Oracle and DB2. But we are not going to have a big database. We choose sqlite. It is a lightweight program which would be very much useful. We have almost completed client side mobile. Almost means more than 95%. We hope to fit sqlite with the cloud. Android does have sqlite libraries. One must work on the same. We hope to complete sqlite job by the end of the week.

This is a water down architecture for our project. Now we are understanding the Android libraries in Java. Main.xml is the file that can be used to store various User Interface components. Also we choose to use MYSQL and work on a network in using a simulator. As using simulator and netwrok is successful one can easily work on the internet. We are just in primitive stages of development. Red5 is one of the best servers for streaming but I would prefere DSS i.e. Darwin streaming server. As browser is flexible to work on we can easily make the browser to streaming one anything. So we would concentrate on Mobile client i.e the Android.

On the 17th we could work on events.