<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hi Gabe,</div><div><br></div><div>The part although not the same website is on;</div><div><br></div><div><a href="https://profiles.google.com/100965631603901259030/buzz">https://profiles.google.com/100965631603901259030/buzz</a></div><div><br></div><div><i>"Another tip is to use <font class="Apple-style-span" color="#0000ff">cacheable='true' </font>attribute of
user xml returned by web service. This will make FS to maintain a local
cache of the account details. The details will stay in cache until
cleared. This means that FS won't be hitting your web app for every
REGISTER request that hoards of SIP UAs are sending, it will ask only
once upon first request. The subsequent requests will be looked up from
cache."</i></div><div><i><br></i></div><div>I'm trying to reduce unnecessary traffic (posts). The dialplan will probably don't change, only the initial servlet path I need to dynamically set. I can add this to my xml as variable and see if there is any change.</div><div><br></div><div>Thanks and have a good Sunday yet!</div><div><br></div><div>Peter</div><br><div><div>On 23 sep 2012, at 03:30, Gabriel Gunderson wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On Fri, Sep 14, 2012 at 11:54 AM, Peter van Raamsdonk <<a href="mailto:peetzer@gmail.com">peetzer@gmail.com</a>> wrote:<br><blockquote type="cite">I tried the mod_xml_curl after studying the wiki. It works like a charm and<br></blockquote><blockquote type="cite">FS post to my java servlet easily (dialplan and user directory).<br></blockquote><blockquote type="cite">I read on a blog there is option 'cacheable=true' to prevent a post every<br></blockquote><blockquote type="cite">time a dial is made, do you know where to put this?<br></blockquote><br>I've never seen this. I know there was some talk about it (I can't<br>remember if it was ClueCon or the mailing list or what). But I think<br>the general consensus was that simple cacheing isn't going to do much<br>good. It's almost like you need to know, based on the POST info if you<br>should cache or not.<br><br>I'd love a link to the blog if you can find it. Meanwhile, I'm<br>running off to the source to see if that's true.<br><br>If it's something you really need, I'd consider adding caching at the<br>webserver layer, take the work of evaluating the request away from<br>freeswitch and move it to another box.<br><br>Also, you could write your own dialplan that worked as a caching<br>layer. First FreeSWITCH hits your custom dialplan, if it returns a<br>cached dialplan you're done. If not, it moves on to mod_curl_xml. And<br>finally, it makes its way to disk if it can't find a suitable<br>dialplan. I've never done it, but I hear it's not that hard to write.<br><br><br>Good luck.<br>Gabe<br><br>_________________________________________________________________________<br>Professional FreeSWITCH Consulting Services:<br><a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>http://www.freeswitchsolutions.com<br><br>FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>http://www.cudatel.com<br><br>Official FreeSWITCH Sites<br>http://www.freeswitch.org<br>http://wiki.freeswitch.org<br>http://www.cluecon.com<br><br>FreeSWITCH-users mailing list<br>FreeSWITCH-users@lists.freeswitch.org<br>http://lists.freeswitch.org/mailman/listinfo/freeswitch-users<br>UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users<br>http://www.freeswitch.org<br></div></blockquote></div><br></body></html>