Re: [aerogear-dev] Android - server endpoint
----- Original Message -----
> If you had some schema describing what you can expect in the
> result, you could use that to generate POJOs and code to
> automatically mashal / unmarshal these. You can also wrap the
> mechanics of HTTP calls away and after done with all that what you
> have is just a class representing a remote service with methods
> taking POJOS that wrap all the mechanics of the remote call and
> return deserialized POJOs back.
A point to keep in mind is that code generation should be our
**last** resort - in a ideal world we have just one client library
that autodiscovers the rest via a single endpoint.
You mean that your javascript module has dependencies specified, and automatically
downloads other javascript modules...
Or you mean that in java client you have a .jar that automatically downloads other jars?
Sounds like module system and bootstrap code that harneses the module system to pull down
all the code.
But how does that address hiding plumbing away from the developer? And productivity
features like typesafety, and codecompletion that IDEs give you?