The problem here is: can opensips query efficiently match another query,
without really building it? If so, per table contexts can be held, and in some
cases a prepared statement can be used in order to bind to it query values
---
Reply to this email directly or view it on GitHub:
Not sure if you mean attempting to cache query results in the event of another
identical query?
If so, you would just need to key the results to say, the MD5 hash of the SQL
query
---
Reply to this email directly or view it on GitHub:
Having configured the rtpproxy module based on the instructions (here:
http://opensips.com.br/wiki/index.php?title=Oopensips_Nat_script_with_RTPPROXY_-_English)
with the addition of a unix socket for timeout notification
When a timeout occurs, the notification is sent to opensips which results
Branch: refs/heads/master
Home: https://github.com/OpenSIPS/opensips
Commit: bfde3a3504b46aac93b31651ee92029adad339e2
https://github.com/OpenSIPS/opensips/commit/bfde3a3504b46aac93b31651ee92029adad339e2
Author: Jarrod Baumann jar...@unixc.org
Date: 2015-04-16 (Thu, 16 Apr
Merged #467.
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/pull/467#event-283815577___
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
@rgagnon24 It's not about the results. It's about matching ,somehow,
efficiently, the keys and values which you receive to build a query, to match
something like a list of prepared statement queries, so you won't need to build
a new one.
---
Reply to this email directly or view it on GitHub:
Using master from commit 24341a06cd18ed32f4d818729122e154e7db520f I am getting
odd error logs from the TLS module.
Apr 17 11:04:08 alpha /usr/local/sbin/opensips[18512]:
ERROR:proto_tls:_tls_read: SYSCALL error - (0) Success
Apr 17 11:04:08 alpha /usr/local/sbin/opensips[18512]:
