Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MongooseIM 2.0.1 #1164

Merged
merged 5 commits into from
Jan 24, 2017
Merged

MongooseIM 2.0.1 #1164

merged 5 commits into from
Jan 24, 2017

Conversation

michalwski
Copy link
Contributor

This release includes:

Special thanks to our contributors: @kenstir, @sstrigler, @igors, @bernardd, @msantos

This release repo history

@fenek fenek merged commit 8f99be5 into master Jan 24, 2017
@fenek fenek deleted the rel-2.0 branch January 24, 2017 12:47
@jonathanve
Copy link
Contributor

jonathanve commented Feb 17, 2017

Hi @michalwski

Regarding REST API Docs and MUC Light for 2.0.1 version, I see REST API endpoints to create a room, invite someone and send messages. Is there any other endpoint(s) not documented for instance to delete a group, update room details, etc.. or is all this functionality available just by raw xmpp; if this is the case, does the new changes for android/ios/web libs include high level functions for this? Thanks!

@michalwski
Copy link
Contributor Author

Hi @jonathanve,

Thanks for contacting us. To be on the same page I need to be sure if you are asking about REST API for clients [1] or for backend services [2]. In case of [1] it is possible to remove room with HTTP's DELETE method, see [3]. The same is not possible (yet) with the REST API for backend services as described in [2].

Other then REST APIs, full MUC light support is possible via XMPP as described in [4].

[1]. http://mongooseim.readthedocs.io/en/2.0.1/REST-API/
[2]. http://mongooseim.readthedocs.io/en/2.0.1/http-api/http-administration-api-documentation/
[3]. http://mongooseim.readthedocs.io/en/2.0.1/swagger/index.html?client=true#/Rooms
[4]. http://mongooseim.readthedocs.io/en/2.0.1/open-extensions/muc_light/

@jonathanve
Copy link
Contributor

Thanks @michalslaski

@michalwski michalwski restored the rel-2.0 branch March 6, 2017 08:05
@jonathanve
Copy link
Contributor

jonathanve commented Mar 8, 2017

HI @michalslaski Setting up a custom schema for MUC Light is quite straightforward with config_schema and default_config. However, when using the API, the new values do not get stored and the values returned by the API do not contain the new values.

https://github.com/esl/MongooseIM/blob/2.0.1/apps/ejabberd/src/mongoose_client_api_rooms.erl#L96
https://github.com/esl/MongooseIM/blob/2.0.1/apps/ejabberd/src/mongoose_client_api_rooms.erl#L115

I can change the code and create a custom one to do it, I just want to know if there is another way to accomplish the functionality without changing the code in the new releases or a config value...

@michalwski
Copy link
Contributor Author

Hi @jonathanve,

I'm really glad to see you are using MongooseIM and its REST API. The first version of the API is very basic. We want to improve and extend it based on customer needs. Your use case is one of the examples we are waiting for!

If this is possible please send a PR with the changes you need. If not I'll make sure this functionality gets into 2.1.0beta1 which we are going to release later this month.

@jonathanve
Copy link
Contributor

Hi @michalslaski,

Is there any friendly way to get how many offline messages are stored in the queues, by user, when using mod_offline module? We are trying to define a good max_user_offline_messages value and get to know which clients are most often offline :)

Thanks for your help!

Sorry for posting the question here, I do not know where else to ask it.

@fenek
Copy link
Member

fenek commented Jun 28, 2017

Hi @jonathanve

The best place is here: https://github.com/esl/MongooseIM/issues :) Can you please create a new issue there?

@jonathanve
Copy link
Contributor

Thanks @fenek Done

#1369

@michalwski michalwski deleted the rel-2.0 branch January 22, 2020 19:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants