I imagine it is so it can remain dynamic. When you change the static XML configs, you need to trigger a reload (you already know this most likely). XML curl doesn't need this at the moment, but would if it cached the results indefinitely in memory. It becomes a tradeoff between efficiency and dynamic behaviour. It might be an interesting XML CURL option to have, but personally, I value having dynamic results higher. You could, however, introduce caching in your XML curl web service layer to introduce efficiency and scalability. On Fri, May 11, 2012 at 8:44 AM, Vik Killa <vipkilla@gmail.com> wrote:
Upon further investigation, it seems all directory parameters and attributes from static XML are stored in memory and can be accessed if XML_CURL fails. This is not true for any directory variables though. Is there a specific reason why FS does not store directory variables in memory when using XML_CURL?
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org