Re: Re: cvs: pear /Services_JSON JSON.php Test-JSON.php

On 3/24/06, Michal Migurski <mike@teczno.com> wrote: > > > Cool. Glad to see this getting into CVS! > > Same here. =) > > > > Three of the votes for this package expressed reservations with > > > putting this package being in the Services category: > > > > > > > > > http://pear.php.net/pepr/pepr-vote-show.php?id=198&handle=wenz > > > http://pear.php.net/pepr/pepr-vote-show.php? > > > id=198&handle=justinpatrin > > > > > > http://pear.php.net/pepr/pepr-vote-show.php?id=198&handle=bolk > > > > > > I share those reservations. Perhaps put it in the Text or HTML > > > categories? Please, a consensus on where to put this should be > > > reached before the first release. > > > > > > > > I was also happy to see this commit. > > Congrats Michal ! > > > > As for other classes, > > I really like to see client executable code included. > > > > For the category, > > if javascript belongs to html , then HTML category. > > That should be, as javascript belongs to public. > > Just not the server of it. > > > > I would add a call for a new role by pear installer , client > > script , as javascript > > > > Should be in some public area. > > I feel the same way - I think all that's needed is a change in > permissions for my CVS directory access, right? Text_JSON makes some > sense... All the XML stuff has its own top-level category, and I feel > that JSON is approx. on the same level as XML though obviously not as > wide-spread. Would it be presumptuous to start a JSON or Javascript > category, that might house an RPC lib and other toys in the future? One comment I'd have, should this be the route taken (and I think this is totally appropriate; JSON is a markup just as XML is), is to separate the current JSON code into its functional elements: Json/Encoder.php Json/Decoder.php and then you'd have: Json/Rpc.php for that fun json-rpc stuff later... :-) -- Matthew Weier O'Phinney mweierophinney@gmail.com http://weierophinney.net/matthew/