Hi ChrisDane. Certainly, there's nothing stopping you from deploying a RemoteServiceServlet and HttpServlet to the same application if I'm understanding you correctly. You can define a wide range of servlets to handle incoming HTTP requests from your mobile app and wire them to the appropriate URLs manually using web.xml. You can also use a framework for this purpose. I believe other developers have had success with Restlet -- links available in http://groups.google.com/group/google-appengine-java/web/will-it-play-in-app-engine .
- Jason On Mon, Jan 11, 2010 at 5:30 PM, ChrisDane <[email protected]> wrote: > Hi there, > > Having a browser client and a phone client(running native app) on the > same data: > > Having GWT RPC returning Ajax data from GAE seems like the perfect > match for a browser client - but I would not use GWT RPS from the > iPhone or Android? > > So, would it be good coding having both a RemoteServiceServlet and a > HttpServlet running in the same App spot. > HttpServlet serving the Phones and RemoteServiceServlet serving GWT > RPC? > > Then how to use RESTful on the HttpServlet? > > Any directions/links or samples? > > Thanks in advance > > Regards > ChrisDane > > -- > 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 > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > >--
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 [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
