Jeffrey C. Ollie wrote: > I've been pretty quiet on the lists for a while, but why are we adding > an XML parser to OpenPBX? I thought that one of the goals of OpenPBX > was to stop doing things like this and relying on external libraries?
Basically for 2 reasons: 1) we need an alternative to take away that crappy config files we are using 2) we have to focus on the real meat While expanding 1) and 2) it turns out that: 1) the real meat on that branch is (will be) sofia (ie: using external libraries) 2) that simple xml parser works quite well and i can use it in a simple way (so i can focus on the real meat) 3) i don't want to spend time to study external XML parsers and validators and implementing it 4) we have had many problems with portability on platforms != Linux and embedding such a small library is not a bad idea if compared to the troubles that MANY people who don't even know how to install an external library from sources can arise, even among the people who should be supposed to work with us (And that seems to work agaings us instead) 5) things like config parsers, memory pools and internal database interaction IMHO are better suited inside of the package. So in conclusion: If someone writes a working XML config wrapper relying on an external library (_the code complexity would be the same, imho_, because that parser that i included is really simple), writes the docs and tests it on all platform and frees me from doing that instead of concentrating on sofia, that is a good point to do it Max P.S.: i have added also some functions (=a library??) to manage memory pools because i didn't find any external and suitable alternative. P.S.2: i'm planning to write an API to manage sqlite databases to store informations for chan_sofia and possibily other things, instead of using opbxdb which is not so flexible as we need. _______________________________________________ Openpbx-dev mailing list [email protected] http://lists.openpbx.org/mailman/listinfo/openpbx-dev
