http://wikis.sun.com/display/Jersey/Overview+of+JAX-RS+1.0+Features
I'm using JAX-RS (Jersey 1.1.5 version) to provide clients with a GData/AtomPub style REST api to their data stored in the App Engine datastore, allowing both XML and JSON CRUD requests to GET, POST, PUT, DELETE data. (Though you may find Restlet a bit easier to use out of the box with Google App Engine at http://www.restlet.org/downloads/testing as you certainly need to use the latest versions of Jersey for it to work.) So, yes, you can produce a web api, and it should be an appropriate platform using Google App Engine. It's really deciding which Java REST or web service framework you like best. Then it's just the same process as building a public facing web application. If your API is allowing bulk updates, then there are existing posts to this group discussing using the Task Queue to keep operation times down. Andy On Dec 17, 5:39 pm, Prashant Gupta <nextprash...@gmail.com> wrote: > Hi, > > I was thinking of developing a web api which will allow web apps to read or > put some data from/to my app. I am not sure what I exactly want to do > because I am not sure how a web API is developed & what are the limitations, > is it same as we write an app? ok, that was a stupid question. I tried to > search some text which could help me get some tips or ideas on web api > development but I couldn't find any :( . I would be thankful if you guys > help me find out some text which could help me with this. Secondly, I was > wondering if App Engine is the right place to host a web api? Experts please > comment on this. > > Thanks. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To post to this group, send email to google-appengine-j...@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
