After some prodding I've checked in a mod_limit which enables a backwards compatible mode for limit behavior. It is a bit noisy with warnings about deprecated calls -- this is to encourage you to migrate. <div><br></div>
<div>It will auto-load mod_db and mod_hash and supports the older calling convention (limit with not backend specified, limit_hash, etc). </div><div><br></div><div>You till need to edit modules.conf to enable building mod_db and mod_hash but your runtime config doesn't need to be updated until you are ready to do so. unloading mod_limit will turn off the older behavior.<br>
<br><div class="gmail_quote">On Sat, Jun 19, 2010 at 11:15 AM, Rupa Schomaker <span dir="ltr"><<a href="mailto:rupa@rupa.com">rupa@rupa.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If you've been paying attention to the conf call or irc you'll know this change was coming. I've committed a significant change to how limits are managed in FreeSWITCH. This change is NOT backwards compatible. It requires one to:<div>
<br></div><div>0) git pull (of course)</div><div>1) rerun ./configure to generate new Makefiles for new modules</div><div>2) edit modules.conf, remove mod_limit and add mod_db and mod_hash</div><div>3) modify conf/autoload_configs/modules.conf.xml, remove mod_limit and add mod_db and mod_hash</div>
<div>4) create/edit conf/autoload_configs/db.conf.xml if using ODBC</div><div><br></div><div>In your dialplan, anywhere you are using limit, you need to add db to the data line. Anywhere you are using limit_hash you need to remove _hash from application and add hash to the front of the data line. Same pattern applies to any API usage of limit you may be using.</div>
<div><br></div><div>Read the wiki at: <a href="http://wiki.freeswitch.org/wiki/Limit" target="_blank">http://wiki.freeswitch.org/wiki/Limit</a> for documentation on limit.</div><div><br></div><div>Ok, why the change?</div>
<div><br></div>
<div>limit has been moved into core with support for pluggable backend limit providers. This allows one to develop limit backends relatively easily and provides a more structured interface to these different limit backends. Expect to see backends provided by more than just db and hash.</div>
<div><br></div><div>It also always bothered me that db and hash were part of the mod_limit module. They are not standalone and provide functionality specific to themselves.</div><div><br></div><div>I've updated the wiki with documentation. I'll continue to update the wiki as necessary, feel free to do so yourself if there is something unclear or missing.</div>
<div><br>-- <br>-Rupa<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br>-Rupa<br>
</div>