Hi Henning,<br><br><br><div class="gmail_quote">On Thu, Mar 19, 2009 at 6:33 PM, Henning Westerholt <span dir="ltr"><<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thursday 19 March 2009, Jason Penton wrote:<br>
</div><div class="im">> This is exactly why we're doing it :D<br>
><br>
> another thing we're looking at is centralising some of the state - like the<br>
> tm module and dialog modules could store data centrally so calls<br>
> (transactions) can be served by any instance of an 'OpenSER cloud'. Havent<br>
> got there yet, but been thinking about it- possibly using something like<br>
> memcached. Would love to work with the list if anyone else has interest.<br>
<br>
</div>Hi Jason,<br>
<br>
this was one of the reason i developed the memcached module, to store global<br>
state like this. One possible next step could be the creation of an interface<br>
to the dialog and tm module to store/ synchronize its cache with it.<br>
<br>
I've investigated a bit the option to create a SQL-like interface on top of<br>
memcached. This would make it quite easy to use it in modules. But it turned<br>
out not that easy, SQL matches not really good to the key-value model which<br>
memcached uses. But i think it should be feasible to generalize the cache<br>
model that is used from dialog and tm, and use this. I can help with the<br>
memcached connection, when somebody has interest to work on the dialog side..</blockquote><div><br>I am going to dig my hands into the dialog module next week. Will let you know how it goes<br><br>Cheers<br>Jason <br></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
Cheers,<br>
<font color="#888888"><br>
Henning<br>
</font></blockquote></div><br>