For me, normally when reading a config, I would read the whole thing to memory, modify what I need to modify, then write the whole thing again to persistent storage. But you know node.js far better than me of course. Right now the objects only provide a whole read indeed. But it is perfectly possible to add, something like, update(), which update the fields selectively as you require. It's just that we don't have it yet. :) Best regards, Benny On Thu, Mar 6, 2014 at 2:34 PM, Brian White <mscdex at mscdex.net> wrote: > My use case is that I'm writing a node.js binding to pjsua2 and it would > make things much easier for the end user if they could just specify the few > config options they would want to change (I'd imagine this would be the > case for the majority of end users) and leave everything else at defaults. > Then I could just pass the JSON directly to the pjsua2 config classes and > even if new options become available in the future, I wouldn't have to > change my code any. > > For now though I guess I will just have to maintain a list of valid config > options for each class and set them manually. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20140310/875ac81d/attachment-0001.html>
