-
Notifications
You must be signed in to change notification settings - Fork 428
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
The second release of mod_mam #151
Conversation
…berd_users_muc.localhost',{<<alicesroom>>,<<muc.localhost>>}],[]} during sending a MUC message.
Added an empty stop_server function.
…reconnecting again. Added supervisor2.
Special entries were added into process dictionary: * mim_host - host of the process; * mim_process_type - category of the process. These tags can be used for debugging, better introspection and logging. Entries should not be used in business logic and/or from inside of the process.
@@ -272,6 +272,8 @@ do_recv(LogFun, RecvPid, SeqNum) when is_function(LogFun); LogFun == undefined, | |||
%% Returns : void() | does not return | |||
%%-------------------------------------------------------------------- | |||
init(Host, Port, User, Password, Database, LogFun, Parent) -> | |||
put(mim_host, Host), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Host is not a MongooseIM host, but MySQL server's IP.
There is a lot of mod_mam_* files right now. What do you think of moving them do a dedicated subdirectory? Or maybe even other repo which will be a dependency for MongooseIM? |
Fixed specs Conflicts: apps/ejabberd/src/mod_mam.erl apps/ejabberd/src/mod_mam_cache_user.erl apps/ejabberd/src/mod_mam_muc.erl apps/ejabberd/src/mod_mam_muc_odbc_arch.erl apps/ejabberd/src/mod_mam_odbc_arch.erl apps/ejabberd/src/mod_mam_utils.erl rebar.config rel/reltool.config
While Base 36 is slightly shorter, Base 32 is easy to read
@arcusfelis, could you rebase or merge with master? |
Fine, I will rebase or merge. |
Git is one thing, but clean code is another thing. Let's put that on vote. Could everyone involved in the project say wether it is good idea to move all |
And here goes my vote: |
👍 for dedicated directory, also 👍 for dedicated directory for |
☝︎ for dedicated dir. Also, it might make sense to move the larger modules into their own |
I hold from voting, but would like to pinpoint that introducing extra dirs per module is repeating history. In pre-fork ejabberd there were actually multiple directories below |
@Lavrin: and the |
Yes, it is.
I think that's better solution. This approach has additional advantage - we can easily add/remove such app from Erlang release making the final release smaller if given big functionality is not required. Good candidates for that are |
The second release of mod_mam
Changelog:
Tests are here