Hi all,
I see what you are saying Rob. I am more specifically referring to using Jersey inside an app/widget on Android to send/receive communications for things like sending a high score of a game, or storing central save data, or for other reasons. Having worked with Jersey/REST for a while now, I find it to be the easiest way to communicate with the server side. I do realize, as you and Paul pointed out, that it doesn't matter what the server is. I just happen to use Jersey as my web/MVC framework as well on the server side as it is a breeze to work with.
The only thing I am concerned about with using Jersey client within an android app is the JAXB stuff. That I haven't dug into yet to figure out if Jersey client would work within the android platform and communicate with JAXB back and forth. I know the server side is fine, just wanted to figure out if on an android device, there might be any "known" limitations anyone has come across with using JAXB and android.. specifically the parsing of JAXB responses from the server?
For my android dev, I don't see the benefit of using the browser as the interface to a server-side "app". I much prefer android apps or widgets to having a user use the browser.
Thank you.
________________________________
From: Robert Koberg <rob_at_koberg.com>
To: users_at_jersey.dev.java.net
Sent: Mon, November 30, 2009 7:20:15 AM
Subject: Re: [Jersey] Jersey and Android platform
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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
For additional commands, e-mail: users-help_at_jersey.dev.java.net