<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
If it is being removed in 1.6, I'm a little concerned since there's no
mention of this when you show the application, nor on voip-info.org.
What application/function is it being replaced by?<br>
<br>
Atis Lezdins wrote:<br>
| On 2/13/08, Rob Hillis <a class="moz-txt-link-rfc2396E" href="mailto:rob@hillis.dyndns.org"><rob@hillis.dyndns.org></a> wrote:<br>
|> -----BEGIN PGP SIGNED MESSAGE-----<br>
|> Hash: SHA1<br>
|><br>
|> Atis Lezdins wrote:<br>
|> | By RealTimeUpdate do you mean func_realtime? It shouldn't care,
as<br>
|> | cache is not implemented in realtime level, but higher
(chan_sip).<br>
|> |<br>
|> | Are you sure you need "sip show XXX load". If you "sip prune"
peer<br>
|> | data, it should be re-loaded on next access.<br>
|> |<br>
|> | What i was suggesting - to dig into chan_sip and create dialplan<br>
|> | application SipPrune(peer) that would prune the peer directly,
by<br>
|> | using corresponding function - sip_prune_peer() in chan_sip.c -
that<br>
|> | way you will gain some extra performance, as there's no
manager/cli<br>
|> | overhead.<br>
|> |<br>
|> | However if you're uncomfortable with C, the app_system
shouldn't cause<br>
|> | any troubles :)<br>
|><br>
|> RealTimeUpdate is more likely to correspond to app_realtime
rather than<br>
|> func_realtime.<br>
|<br>
| As to my knowledge - that is obsolete and being removed in 1.6,<br>
| func_realtime replaces it. That's why i wondered about name - I just<br>
| never happened to use it :)<br>
|<br>
| Regards,<br>
| Atis<br>
|<br>
|<br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v1.4.7 (GNU/Linux)<br>
Comment: Using GnuPG with Remi - <a class="moz-txt-link-freetext" href="http://enigmail.mozdev.org">http://enigmail.mozdev.org</a><br>
<br>
iD8DBQFHsnaM6uKn5cBSgGQRAo/TAKDCruPrn2nm2XV/PYbfSuBKA0j5OwCfQ/Ox<br>
QE3SYEmZ01QHUT4ITwmLnT0=<br>
=SKEW<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>