On Jun 29, 2009, at 18:13 , Andreas Junghans wrote:
> Hi Jean-Baptiste,
Hi Andreas,
[CUT]
>
> Anyway, why are you so keen on replacing the low-level JSON lib on the
> Java side? What's wrong with the one from json.org? I'd say "never
> touch a running system" in this case, except there's something
> seriously wrong or missing from the json.org version.
>
In fact, you are right !
JavaRPC can be seen as 2 parts :
a. The RPC one : the servlet, the service and method call
management, ...
b. The JSON<->Java serialization.
I'd like as a first step not to change anything and just use it but
only a. works perftly for me and I encountered issues with b.
The big plan, for me, is the following :
1. Just use it and do things with it this summer
2. Write test, say in september
3. Think to refactor based on the experience of 1 with the security of
2, say in october.
So, maybe, I'll start again from sracth with pure JavaRPC and report
issue I have with b. here rather than trying to use it, refactor it at
the same time :-)
For now, I'm sure some issue I had was due to my lack of knowledge of
JavaRPC usage.
BTW, what about the transient Java keyword ? Are transient attributes
excluded from json serialization ?
------------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
