I am with Senaka on this one. Agreed C5 is a major shift, but what's the advantage a user has in using JSON for config files ? This would be a huge migration effort (for them and us) and after those are just, well property files. Most customer prefer the simple name=value paradigm. Getting them to edit JSON files for any system property seems a stretch. Would JSON be script friendly ? Puppet/Chef friendly ?
Also, the target audience for those files are DevOps, not web developers (reference to the Jaggery discussion before). Isabelle. ------ Isabelle Mauny Director, Product Management; WSO2, Inc.; http://wso2.com/ email: isabe...@wso2.com <isabe...@wso2.com> - mobile: +34 616050684 On Tue, Mar 12, 2013 at 4:02 PM, Senaka Fernando <sen...@wso2.com> wrote: > Hi Azeez, > > More than docs, we need to consider the user experience aspect. People are > using these things in real production environments. Some have scripted > their deployments. How much of an effort is it to move from XML to JSON in > that sense? I think that's not straightforward. Also, we use XML all over > the place. Ex:- Synapse Config, Registry Handlers, Lifecycles, Endpoints - > basically everything configuration across every single component is XML. > Unless everything becomes JSON, the users have to train themselves to do > two things. So, what looks cool to us does not look so cool to everybody. > So, its not just kernel that we need to think about, its the whole > platform. Unless we have a platform-wide move, I'm -0 for this. > > Also, based on the last internal discussion on this, Paul said, "Plain > JSON is worse than plain XML", IIRC. I thought we agreed for configuration > files like the LB model in that discussion, but again that would mean > custom parsers, custom work, and adoption across the entire platform. > > Thanks, > Senaka. > > On Tue, Mar 12, 2013 at 6:38 AM, Afkham Azeez <az...@wso2.com> wrote: > >> I agree on the points everybody has mentioned in support of XML in config >> files. >> >> But it seems that most people still don't understand that Carbon 5 is >> going to be a major shift. We are removing the Axis2 dependency from the >> kernel, and minifying the kernel. Lots of things starting from some package >> structures will be changed. Docs will need updating. From Carbon 4.0 to 5.0 >> is going to be a major leap. >> >> Azeez >> >> >> On Tue, Mar 12, 2013 at 6:53 PM, Maninda Edirisooriya >> <mani...@wso2.com>wrote: >> >>> I think JSON is more human readable than XML, as it is cleaner than XML. >>> (I may be wrong as I am familiar with JavaScript) And as Nuwan said we will >>> not get the "Everything JSON" feeling. But many web developers will be much >>> familiar with JSON than XML as Jaggery and JavaScript are JSON based. But >>> there is still a major XML dependancy, that is web services. As all the web >>> services are still comes with XML, "JSON Everyware" story will not be >>> complete. So I prefer moving to SOAP based web services to REST/JSON based >>> system rather than changing configs from XML to JSON. The reason is current >>> XML configs has no major problem and changing it will course lot of bugs >>> and support issues. We can postpone this until XML becomes a unpopular >>> language which will not happen in near future. Until that we can work on >>> changing message protocols from XML/AXIOM to REST/JSON and improve the >>> performance and simplicity of the implementation in ESB and AS. >>> >>> >>> *Maninda Edirisooriya* >>> Software Engineer >>> *WSO2, Inc. >>> *lean.enterprise.middleware. >>> >>> *Blog* : http://maninda.blogspot.com/ >>> *Phone* : +94 777603226 >>> >>> >>> On Tue, Mar 12, 2013 at 4:45 PM, Sagara Gunathunga <sag...@wso2.com>wrote: >>> >>>> >>>> >>>> On Tue, Mar 12, 2013 at 12:41 PM, Afkham Azeez <az...@wso2.com> wrote: >>>> >>>>> Folks, >>>>> I am starting a new thread to see how everybody feels about using JSON >>>>> syntax for the config files wer are using. I personally feel that it looks >>>>> elegant, and very easy to edit with vi. Also, we don't do any schema >>>>> validation of our config files, and the config file structures are simple, >>>>> so JSON could be more appropriate. >>>>> >>>>> Thoughts? >>>>> >>>> >>>> >>>> I'm -0 on this change. >>>> >>>> Other than user friendliness do we have any significant customer >>>> related issue to fix by changing configuration files into JSON ? If not we >>>> should target to solve significant C4 issues first. As some people >>>> mentioned this needs great amount of documentation and migration tools, I >>>> don't believe it's a good idea to do this at the beginning of C5. >>>> >>>> Thanks ! >>>> >>>> >>>> >>>> >>>>> >>>>> -- >>>>> *Afkham Azeez* >>>>> Director of Architecture; WSO2, Inc.; http://wso2.com >>>>> Member; Apache Software Foundation; http://www.apache.org/ >>>>> * <http://www.apache.org/>** >>>>> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >>>>> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >>>>> twitter: >>>>> **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >>>>> * >>>>> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >>>>> * >>>>> * >>>>> *Lean . Enterprise . Middleware* >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> architect...@wso2.org >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Sagara Gunathunga >>>> >>>> Technical Lead; WSO2, Inc.; http://wso2.com >>>> V.P Apache Web Services ; http://ws.apache.org/ >>>> Blog ; http://ssagara.blogspot.com >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> _______________________________________________ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > * <http://wso2con.com/> > * > * > > Senaka Fernando* > Member - Integration Technologies Management Committee; > Technical Lead; WSO2 Inc.; http://wso2.com* > Member; Apache Software Foundation; http://apache.org > > E-mail: senaka AT wso2.com > **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 > Linked-In: http://linkedin.com/in/senakafernando > > *Lean . Enterprise . Middleware > > _______________________________________________ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
