Re: Future of jabberd

2016-05-30 Thread brahmann

Hi, about all - good direction i think!

1. Event-driven single - good choice.
2. There are alot of other good libraries like libev too, but libuv - 
good, used it in my work pretty stable with 300-1000 events per loop. 
But last time we using libev coz FreeBSD releated more.
5. About js, logic on js, imho not good idea... jabberd2 good production 
class jabber server and its working on my work environments alot of 
years. Time for this will be when jabberd2 will be singleprocess and 
need to fork it to jabberd2-js port with XEP-logic on js. But not change 
good product... imho


I can help with testing and maybe this summer alittle with coding.. this 
email is jabber too for connections


Thank you for developing Jabberd2

wbr, brahmann

On 30.05.2016 11:31, Tomasz Sterna wrote:

There are some things we already talked about on Gitter channel [1],
but I would like to raise them on the ML for peer review.

As you can see from late activity, jabberd2 project is far from dead.
With the inclusion of new features like WebSocket support, C99 code
compatibility, IPv6 improvements, modern TLS handling, SASL Anonymous,
password hashing, CRAM-MD5 and more... it is not a stale codebase
anymore.

But it is far from modern too...
There are some changes I would like to introduce in the near future and
I would like to hear your thoughts about:


[SKIP]


What do you think of these ideas, guys?
Do you have any suggestions for even more disturbing improvements? :-)
I would love to hear all feedback.

You may take a look at experimental/PoC codebase at ashnazg [10] branch on 
GitHub.


[1] http://gitter.im/jabberd2/jabberd2
[2] http://en.wikipedia.org/wiki/Message-oriented_middleware
[3] http://www.mbus.org/
[4] http://nanomsg.org/v0.9/nn_bus.7.html
[5] http://duktape.org/
[6] http://log4c.sourceforge.net/
[7] http://libdbi.sourceforge.net/
[8] http://github.com/antirez/sds
[9] http://www.gnu.org/software/libunistring/
[10] http://github.com/jabberd2/jabberd2/tree/ashnazg






Re: Future of jabberd

2016-05-30 Thread brahmann

Agree (web).
I wrote some years ago simple web interface for jabberd2, need to review 
it and rewrite for new one later. Its will be good for those who want it 
but not in jabberd2 code inside.


Using it with mysql and postgresql - works perfectly


wbr, brahmann

On 30.05.2016 16:43, li...@lazygranch.com wrote:

Regarding item 4, seriously, does everything ‎these days have to have a web 
interface? It just increases the attack surface. Adding a web interface means 
one more thing to protect against hackers, which means writing rules for the 
WAF or adding something else for fail2ban or sshguard to watch.

Most services have a "reload" and "restart" in the service command. It really 
isn't a burden to use them. The burden is to have yet another means to restart the service.

Personally, I viewed the XML setup as a feature since it is self documenting.

My preference would be for better sqlite support. That is add and delete users 
from sqlite3 rather than mysql.