<br><br><div class="gmail_quote">On Thu, Jun 11, 2009 at 11:24 AM, John Dalgliesh <span dir="ltr"><<a href="mailto:johnd@defyne.org">johnd@defyne.org</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;">
On Thu, 11 Jun 2009 at 10:42 -0700, Michael Collins wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Thu, Jun 11, 2009 at 10:33 AM, Michael Giagnocavo <<a href="mailto:mgg@giagnocavo.net" target="_blank">mgg@giagnocavo.net</a>>wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Exactly. You probably want to have something like this anyways, so that<br>
when someone accidentally unplugs the system, or the disks/CPU/RAM crash,<br>
you’re not stuck.<br>
<br>
<br>
<br>
That is, until FreeSWITCH can record its internal state to some<br>
inter-machine memory so we can have hot failover. ;)<br>
<br>
<br>
<br>
</blockquote>
I think that's going to be in 1.0.5. :)<br>
</blockquote>
<br>
I'm still too much of a noob to be certain that's a joke :) ... but FS core already does record much of its internal state... to a DB, right? It just has to not clear that out on startup and problem solved!<br>
</blockquote><div>It was a joke. :)<br></div></div><br>