Tomasz Sterna
Tomasz Sterna
Building a release is trivial. I will do it. (Also, you don't have my PGP key to generate the signatures ;-) ) > - Cleanup configure.ac and the build system....
Please do. I have no problem in adding repo write rights to the people submitting consistently good PRs. And if you live up to your promises, I will gladly transfer...
I don't like the idea of introducing DB connection in router. DB interface is known for introducing heavy slowdowns in SM component. But it may be worth putting this patch...
Possibly. But I'm rather for implementing a logging component and delivering it in jabberd2 codebase. One of backends used by this logging component could be XEP-0136 compatible.
Looks like it is ejabberd issue: https://support.process-one.net/browse/EJAB-1590
I'm sorry, but I don't fully understand what exact change you are proposing.
What use case do you have for such module?
Jappix uses PEP, which does publishing on user JID nodes and does not require separate pubsub component. jabberd2 has PEP module started: http://github.com/jabberd2/jabberd2/blob/master/sm/mod_pep.c
Other approach is to introduce worker threads in components, so only one worker thread would get stopped on DB access. But jabberd2 single thread by design nature, could make adding...
- https://www.postgresql.org/docs/8.0/static/libpq-async.html - https://www.percona.com/live/mysql-conference-2014/sessions/asynchronous-mysql-how-facebook-queries-databases - https://www.sqlite.org/asyncvfs.html