Ok, I've started to take a look at all this. JSON seems very easy to understand, but I don't have much experience with it. My lack of experience is what is guiding my decisions. In other words: I don't know how to create the "perfect" interface, and I don't know what to trust. So, I've tried to expose only the bare minimum of what I need just to get my own things done.
Another issue is that I'm not convinced that the json-lib is something that we'll want to use forever; at the same time, though, I have no idea what kind of interface we'll want to be "stuck" with. So, that leaves two ways of going about things: (1) either provide access to json-lib "as is", or provide a more generalized interface (and therefore adapter) to "a JSON service" whereby the implementation can be switched later while keeping the same interface. With all the above in mind, I've decided on the second approach. In any case, when I'm done, I'll commit to the lab and you can make the decision for yourself as to whether or not this bundle is useful. If it is, by all means, please play with it. If not, then you can just ignore it. ;-) I don't plan to commit for another few days, though, until I at least get all the stuff done with JSON that I wanted to do. Cheers, Dave > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Rick Litton > Sent: 1 May 2007 10:23 > To: General OPS4J > Subject: Re: Talk of JSON > > > Hi David, > > Yes, we have started to use json-lib but we haven't started to > bundlelize it > yet. So do keep us posted of your progress. Thanks. > > -- rick _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
