I would love to see a SQL engine, a real one, being pulled inside Opensips. Right now I have to use unixODBC and execute a stored procedure 3000 times per second, only to achieve a routing decision. It is very inefficient. Some engines like RocksDB, open-source, should be part of Opensips and run in the same process space. This would be a first for any softswitch technology. We need full SQL technology, with tables, views, stored procedures, functions, timers, etc. Philip Orleans
On Thu, Dec 3, 2020 at 5:49 AM Bogdan-Andrei Iancu <bog...@opensips.org> wrote: > Gentle reminder, > > We do not want you to miss your favorite feature for 3.2 and the we are > getting closer and closer to closing this poll. > > Best regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Bootcamp 2020 online > https://opensips.org/training/OpenSIPS_eBootcamp_2020/ > > On 11/19/20 2:00 PM, Bogdan-Andrei Iancu wrote: > > Hi OpenSIPSers ! > > > > Is it the time to turn our eyes to the next major release, to OpenSIPS > > 3.2 . Is it the time to plan it, to decide what should be the main > > area to focus on when developing OpenSIPS 3.2, to decide what ideas > > and features just be counted when putting together the roadmap for 3.2. > > > > So, we want to take the community pulse on the upcoming 3.2. Any > > suggestions, ideas, opinions are (as always) more than welcome for us > > and for the project. So, make your statement and please fill in this > > short (but relevant) form : > > > > https://bit.ly/2ISE9uX > > > > Best regards, > > > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users >
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
