On Nov 30, 2009, at 1:37 AM, Kevin Duffey wrote:
> I thought using Jersey client was pretty easy already... is there a reason you'd suggest using html/javascript over using jersey since I am working in java and the android device would really be a client app communicating with a server that is also java based?
As Paul mentioned, it doesn't matter that the server is java. You are connecting over HTTP. You client can be written in anything that can communicate over HTTP (e.g. ajax/javascript).
But, fwiw and mostly off topic:
I just did a phone app (for Symbian OS) and during development it was very easy to to just load/refresh the page off of the webserver rather packaging and deploying the app. Once everything is set, then package/deploy. The app looks just as good as a native app (maybe better?).
You can set up auto update by storing the JS, CSS in a property. At app start, asynchronously check a URL for a version. If the one on the server is newer, update the stored property (and of course the page) with the new code.
best,
-Rob
>
> From: Robert Koberg <rob_at_koberg.com>
> To: users_at_jersey.dev.java.net
> Sent: Sun, November 29, 2009 1:21:35 PM
> Subject: Re: [Jersey] Jersey and Android platform
>
>
> On Nov 29, 2009, at 12:56 PM, Kevin Duffey wrote:
>
> > Hey all,
> >
> > I am messing around with Android when time allows, and am curious if the jersey client code would work within an android application as it is so I can make RESTful calls to a jersey server, or not? Has anyone played around with this yet, or might know if there would be any limitations... or perhaps incompatibilities?
>
> A simpler way would be to use HTML and javascript. Check out:
>
> http://www.phonegap.com/
>
> I wish it would on the symbian OS.
>
> best,
> -Rob
>
>
> >
> > thanks.
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>
>