Re: Future of jabberd
On Mon, May 30, 2016 at 9:32 PM, Tomasz Sternawrote: > W dniu 30.05.2016, pon o godzinie 10∶31 +0200, użytkownik Tomasz Sterna > napisał: >> 7. DBI interface to RDBM. > > Just one more question. > > Do you (ML) have a use case for having SM storage in SQL? > Is it just for distributed SM only? > Maybe it is not worth the effort and we should just drop it and embed > something like LMDB [1] in? > > I do see value of having SQL backend for authreg, to integrate with > existing userbase, but SM storage? Does it really need to be > abstracted? > > > [1] https://en.wikipedia.org/wiki/Lightning_Memory-Mapped_Database > > -- > /o__ > (_<^' The best cure for insomnia is to get a lot of sleep. -W.C. Fields > Congratulations - you have Jabberd3 outlined, um.. so long as the name isn't taken yet? In terms of "heavy", if it runs in OBSD on a BeagleBone Black or Debian on a Rasperry Pi Zero, then I think you're OK. Running on an Arduino is a special type of crazy - not that i wouldn't mind seeing it done. Running Jabberd3* as part of a website would be a new kind of distributed. If going full Javascript - this might be interesting: http://electron.atom.io/ In any case - Thank You very much for a great XMPP server - keep having fun *just trying it on - Jabberd11? too binary?
Re: Working around client bugs in server software
On Fri, Oct 12, 2012 at 6:27 AM, Tomasz Sterna to...@xiaoka.com wrote: Dnia 2012-10-12, pią o godzinie 14:50 +0200, Alexandre Jousset pisze: According to this link the bug is marked as resolved, fixed. Do you think clients haven't upgraded and still have the bug? asmack was patched in Beem only. Maven repos still have Smack 3.2.1. So unfortunately - most Java code using Smack still has this bug. And more importantly - this is just an example serving me to ask a broader question. -- Tomasz Sterna Instant Messaging Consultant : Open Source Developer http://tomasz.sterna.tv/ http://www.xiaoka.com/portfolio Are you suggesting the server have an auditbot to evaluate the quality of clients and maintain patches that may be requested from the server's admin? If the world is righteous, no bother no fuss - if the world has fallen, there is a way up and the local admin gets notice. If the local admin knows his clients aren't righteous, deployment with patches should be an option. A good ontology for this is EARL http://www.w3.org/WAI/intro/earl This would make each jabberd2 server a QA tool.. :) there be statistics thar
Re: releases plans
2012/3/21 Marek Červenka marek.cerve...@fpf.slu.cz: Dne 21.3.2012 16:17, Tomasz Sterna napsal(a): Dnia 2012-03-21, śro o godzinie 15:13 +0100, Adrian Reber pisze: Seeing all the changes which have been committed since 2.2.14 I am wondering if there are any plans for a new release? Yes... I have one more feature in cooking though. Once it is done it may even yeld a 2.3 release :-) But since you mentioned... It may be worthwhile to do one more 2.2 line release with already committed bugfixes. What do you think, community? release early, release often ;) +1 release early, release often ;) much thx (on Fedora OpenBSD)