The biggest disadvantage I see is that there is no straightforward way to have comments in the JSON file.
Azeez On Tue, Mar 12, 2013 at 2:59 PM, Nuwan Bandara <nu...@wso2.com> wrote: > Hi Azeez, > > I remember we were having same kind of a discussion some time back, > but couldn't find the thread :( > > So before jumping to the JSON bandwagon, we have to evaluate the > advantages we are hoping to gain by converting all files to JSON. Dont get > me wrong I like json more than xml but that's mainly because we are using > json effectively in javascript/jaggery. But in Carbon we don't get that > advantage unless we are going to rewrite everything in maybe node (or > something similar). > > For me personally XML is more human readable than JSON, and if you think > about converting config files like identity.xml/carbon.xml etc we will have > to invest some time and carefully design the JSON configs so it is simple > and readable. So compared to the effort do we have enough advantages of > doing this. > > Regards, > /Nuwan > > > On Tue, Mar 12, 2013 at 2:18 PM, Afkham Azeez <az...@wso2.com> wrote: > >> >> >> On Tue, Mar 12, 2013 at 2:14 PM, Eranda Sooriyabandara >> <era...@wso2.com>wrote: >> >>> Hi Azeez, >>> >>> >>>> 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. >>>> >>> >>> 0, Using JSON for configuration files gives an advantage, but is it >>> worth the effort need to change the documents, migration etc...? >>> >> >> This is Carbon 5. This is where we are doing major platform enhancements. >> A lot of documents will have to be changed with Carbon 5. >> >> >>> >>> thanks >>> Eranda >>> * >>> * >>> >>> _______________________________________________ >>> 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* >> >> _______________________________________________ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > *Thanks & Regards, > > Nuwan Bandara > Associate Technical Lead & Member, MC, Development Technologies > WSO2 Inc. - lean . enterprise . middleware | http://wso2.com > blog : http://nuwanbando.com; email: nu...@wso2.com; phone: +94 11 763 > 9629 > * > <http://www.nuwanbando.com/> > -- *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*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
