Project

General

Profile

Is it possible to filter out 'muc-allow-chat-states' for Occupants who become offline?

Hamid Alimohammadi
Added almost 4 years ago

Hi,

Is it possible to filter out and disable 'muc-allow-chat-states' options for users who become offline?

Actually I have added the following two lines to the init.properties file:

muc/default_room_config/muc#maxhistoryfetch=500

muc/muc-allow-chat-states[B]=true

The 'muc-allow-states' is very useful for online room occupants; However, when an occupant becomes offline the 'muc-allow-states' statuses like "composing" and so on are saved in the DB and when (in the client software) a 'history-since' is requested, all the 'muc-allow-states' like "composing" are retrieved from DB which are some how over head both for DB and client software.

Is there any way to have 'muc-allow-chat-states' & 'history-since' options only for Online users and omit it for Offline users?

Bellow is the init.properties file:

config-type=--gen-config-def

--admins=admin@test.com

--virt-hosts=test.com

--vhost-anonymous-enabled = false

--user-db-uri=jdbc:mysql://10.10.10.75/tigasedb?user=tigase&password=tigase12

--user-db=mysql

--cluster-mode=false

--debug=server,db,archive

--monitoring=jmx:9050,http:9080,snmp:9060

--sm-plugins=+message-archive-xep-0136,+jabber:iq:auth,+urn:ietf:params:xml:ns:xmpp-sasl,+urn:ietf:params:xml:ns:xmpp-bind,+urn:ietf:params:xml:ns:xmpp-session,-jabber:iq:register,+jabber:iq:roster,+presence,+jabber:iq:privacy,+jabber:iq:version,+http://jabber.org/protocol/stats,+starttls,+amp,-msgoffline,+vcard-temp,+http://jabber.org/protocol/commands,+jabber:iq:private,+urn:xmpp:ping,+basic-filter,+domain-filter,+pep,-zlib,+jabber:iq:last

--amp-security-level=NONE

--comp-class-6=tigase.archive.MessageArchiveComponent

message-archive/archive-repo-uri=jdbc:mysql://10.10.10.75/tigasedb?user=tigase&password=tigase12

--message-archive/auto=true

c2s/watchdog_delay[L]=60000

c2s/watchdog_timeout[L]=40000

c2s/watchdog_ping_type=xmpp

c2s/max-inactivity-time[L]=100

sess-man/plugins-conf/message-archive-xep-0136/required-store-method=body

sess-man/plugins-conf/message-archive-xep-0136/component-jid=message-archive@test.com

c2s/processors[s]=urn:xmpp:sm:3

muc/default_room_config/muc#roomconfig_persistentroom=true

muc/default_room_config/muc#roomconfig_publicroom=false

muc/default_room_config/muc#roomconfig_membersonly=true

muc/default_room_config/muc#roomconfig_changesubject=true

muc/default_room_config/muc#maxhistoryfetch=500

muc/default_room_config/muc#roomconfig_roomname=Group

muc/muc-allow-chat-states[B]=true

--comp-class-1=tigase.muc.MUCComponent

--comp-name-6=message-archive

--comp-name-1=muc


Replies (4)

(1)
Avatar?id=6098&size=32x32

Added by Bartosz Małkowski TigaseTeam almost 4 years ago

I don't understand!

If user goes offline, then he is removed from room. So no more messages should be transmited.

(1)
Avatar?id=6023&size=32x32

Added by Artur Hefczyc TigaseTeam almost 4 years ago

Bartosz, I think this is just about storing room chat history in DB. Hamid suggests that chat states should not go to chat history repository (memory or DB), and then should not be sent to a user who just joins the group chat. I think it makes sense.

(1)
Avatar?id=6098&size=32x32

Added by Bartosz Małkowski TigaseTeam almost 4 years ago

Currently it is imposiible. It have to be implemented (or rather current implementation must be changed).

Added by Hamid Alimohammadi almost 4 years ago

Thank you both of you for reply.

    (1-4/4)