Hello all,
I have a few questions about virtual hosts, hope you can help me:
I would like to have many virtual hosts in the same ejabberd installation, each using its own My SQL database. However, I want all of them to have the same users table, so a registered user could log in any of the hosts with the same user ID and password. Since I won't allow any of the hosts to create or edit user accounts, I thought I could create the users table in each database as a view of a central table. Is there a better way of achieving what I want?.
The number of virtual hosts could eventually reach hundreds or thousands (can't tell you why). Is there any limitation or performance issue about using so many hosts?.
The information about ejabberd 3.0.0 says it will support 'Massive Hosting'. Can anyone give more information about it?.
Thank you,
Iván
Ivan Martinez wrote: I would
I would like to have many virtual hosts in the same ejabberd installation, each using its own My SQL database. However, I want all of them to have the same users table, so a registered user could log in any of the hosts with the same user ID and password. Since I won't allow any of the hosts to create or edit user accounts, I thought I could create the users table in each database as a view of a central table. Is there a better way of achieving what I want?.
In ejabberd you can define a different ODBC database for each vhost, but not a different database for each table in the vhost. Your trick seems the better solution, as it's performed outside ejabberd.
ejabberd 2 doesn't take care to create or delete tables, only cares about reading and writting to them. If your trick allows ejabberd to read the information correctly, then it will work.
The number of virtual hosts could eventually reach hundreds or thousands (can't tell you why). Is there any limitation or performance issue about using so many hosts?.
Not implemented limitations, so it's just the performance limits, as ejabberd 1 and 2 was not designed for so many vhosts. However, in the last months some people contributed a few optimizations, so maybe ejabberd 2.1.5 can handle some high number of vhosts.
The information about ejabberd 3.0.0 says it will support 'Massive Hosting'. Can anyone give more information about it?.
For ejabberd 3, all the possible bottlenecks for running many vhosts have been rewritten to ensure it supports high number of vhosts.