Add support for XEP-0313: Messege Archive Management (#28)
Closed
Andrzej Wójcik (Tigase) opened 8 years ago
Due Date
2016-07-24

I think it may be good idea to add support for MAM as from what I see it is more often used/supported on client side than XEP-0136 Message Archiving - maybe due to fact that implementation of this protocol is easier.

Artur Hefczyc commented 8 years ago

From what I can see MAM is kind of a subset of of our MA and UA implementation. Do you think it is possible to implement MAM somehow on top of our UA, so the storage would be the same and only access to the storage would be different through a different protocol. This would be an optimal approach in my opinion.

Andrzej Wójcik (Tigase) commented 8 years ago

%kobit Yes, I suppose it is possible. My idea was just to add another XEP which would internally use same tables and maybe even same implementations of repositories.

Andrzej Wójcik (Tigase) commented 8 years ago

I suppose it will be better to do this after updating MA and UA components to work as components based on kernel and beans as this will be default and preferred way to implement components in 7.2.0. Right now in master branch of Tigase XMPP Server we have this feature almost ready, so it will be good to add features after changes in implementation of base component.

%kobit Do you agree? I so I would need to adjust due date.

Artur Hefczyc commented 8 years ago

OK

Andrzej Wójcik (Tigase) commented 8 years ago

I implemented support for MAM protocol in MA and it works well.

During this implementation I needed to refactor few things to make this implementation possible. Due to this fact I also needed to refactor UA to make it work with modified MA.

After all this changes I created test cases in TTS-NG to confirm that implementation of MAM and XEP-0136 works properly in MA and that UA also works as expected.

All tests passes so I'm closing this task.

issue 1 of 1
Type
New Feature
Priority
Normal
Assignee
RedmineID
4242
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/tigase-message-archiving#28
Please wait...
Page is in error, reload to recover