On Fri, Sep 14, 2012 at 11:54 AM, Peter van Raamsdonk <peetzer@gmail.com> wrote:
I tried the mod_xml_curl after studying the wiki. It works like a charm and FS post to my java servlet easily (dialplan and user directory). I read on a blog there is option 'cacheable=true' to prevent a post every time a dial is made, do you know where to put this?
I've never seen this. I know there was some talk about it (I can't remember if it was ClueCon or the mailing list or what). But I think the general consensus was that simple cacheing isn't going to do much good. It's almost like you need to know, based on the POST info if you should cache or not. I'd love a link to the blog if you can find it. Meanwhile, I'm running off to the source to see if that's true. If it's something you really need, I'd consider adding caching at the webserver layer, take the work of evaluating the request away from freeswitch and move it to another box. Also, you could write your own dialplan that worked as a caching layer. First FreeSWITCH hits your custom dialplan, if it returns a cached dialplan you're done. If not, it moves on to mod_curl_xml. And finally, it makes its way to disk if it can't find a suitable dialplan. I've never done it, but I hear it's not that hard to write. Good luck. Gabe