On 20.6.11 12:36, Stefan Guggisberg wrote:
On Mon, Jun 20, 2011 at 12:21 PM, Michael Dürig<mdue...@apache.org> wrote:
why JSON strings?
- easy portability
- remoting-friendly
- leads to very compact API
- JSON parsing/generating overhead is IMO minimal
and probably more effecient than creating (and collecting) tons of
small java objects on the heap
I doubt this. In fact I think the situation with the small Java objects is
even worse in the face of a JSON based API: typically a (de)serialization
layer will create an additional set of intermediate objects which have to be
consumed/translated into the domain objects of the respective
implementation.
that's IMO implementation specific. the JSON response doesn't need to
be parsed fully, the JSON string might just as well be kept instead and
domain objects would be generated on demand from the underlying JSON data.
I very much doubt that this will work out. And it is completely opposite
to what the current prototype looks like. Both, above and below the
microkernel api.
Michael
Michael
