6 Commits (master)

Author	SHA1	Message	Date
Victor Seva	dde6a2ff9b	TT#96550 mod_muc interface changed since 0.11.0 ... Change-Id: I27e95a26a688afabbb071ad1d9e1d674627f2417	5 years ago
Richard Fuchs	bffc901a12	TT#34705 merge https://github.com/sipwise/prosody/pull/3 ... squashed commit of commit 4a38d9ad2b (HEAD -> master) Author: Victor Seva <linuxmaniac@torreviejawireless.org> Date: Mon Mar 26 14:15:41 2018 +0200 [sipwise_redis_sessions] clean previous local sessions on start commit a514e6b60d Author: Victor Seva <linuxmaniac@torreviejawireless.org> Date: Mon Mar 26 14:08:31 2018 +0200 [mod_shard] clean redis info on shard/send error if We can't connect to a shard node, clean that info from redis depending on the stanza MUC, persistent rooms are always defined in muc module on start, so don't check for them locally, set as local in redis if no other node has it closes #3 Change-Id: I33b32dacb6aa4010d520c1d04ef81736d6555370	7 years ago
Victor Seva	d346079131	MT#16059 mod_sipwise_pushd: support groupchat messages ... - No need to save MUC participants on redis the message will be processed by sipwise_pushd module at the server that has the MUC room in memory - Load sipwise_pushd module at 'conference.' host if is enabled at the config in order to process 'message/bare' events to catch MUC messages - fix shard when subscriber offline Change-Id: I9d56b3867075d496135ff5b530cc6b23aa16b987	10 years ago
Victor Seva	320bdefb33	MT#16059 save MUC participants on redis too ... Change-Id: I4c5e22d93f966637abe304a6e7fbc88609017a31	10 years ago
Victor Seva	babc44fb9b	MT#6407 support MUC on cluster ... Change-Id: I6d8cc8976ca32bb2af379e2bce9aae38551c7928	10 years ago
Victor Seva	c5f0784ceb	MT#6407 cluster using mod_shard* as base ... 5d5ee8db0d https://groups.google.com/d/topic/prosody-dev/X99ktLm0JwU/discussion TODO: deal with MUC Change-Id: I1dbbe0075e3ca2ba28998a2d2f3396ab4293dbfb	10 years ago