Should i use app engine endpoint models in my android application?
I've been trying out google app engine endpoints api as a backend for a
new project. The app engine project is working fine, but i'm struggling to
find information about how to structure my android application.
I've moved all my data models from the android project over to the app
engine project for the purpose of creating Endpoints. However i've created
multiple endpoints for the same entity, for example i've created one
searchEndpoint and one personEndpoint for the same model Person.
When I generate client libraries i get multiple Person models in the
android application. This means that i can't really use the model in my
android application.
So my question is: Is it recommended to use the endpoint models on the
client side? Or do i need to create wrapper classes on the backend side
and convert them to my own model on the android application.
It seems like the point of using the client libraries over a normal
HTTPRequest disappears if i don't use the model classes directly.
No comments:
Post a Comment