On Thu, Jul 29, 2010 at 02:21, panyasan <[email protected]> wrote:
>
> Since Martin has mentioned that the json-rpc layer will be rewritten to
> conform to spec 2.0 and to remove non-standard behavior, I wanted to
> discuss
> the following point ahead of time:
>
> At least two things are "non-standard" in the current implementation that
> Derrell has designed: the JSON date encoding and the "server_data" property
> of the jsonrpc request. I don't have strong opinions on the Date issue -- I
> know Derrell does ;-)
>
My opinion has changed. I believe we should be fully standards-compliant by
default. That applies to both the missing date functionality that we've
kludged in, as well as server data. The loss of each of these will be a
large burden on many applications, but in the long run, I think that
standardization outweighs the usefulness of these features.
We must, until at least version 2.0 retain the capability of using the now
"qooxdoo standard" additional features, via a mixin or other mechanism. That
functionality has been in the code for many years, and there are too many
potential users of it to simply drop it in any 1.x version. It will be a
significantly major and obtrusive change that does not belong in anything
other than a major version number (1st digit) release.
Derrell
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
