Add back the option to set jicofo as XMPP server component

Currently, we use ejabberd instead of prosody, and ejabberd handles jicofo as a component perfectly. However, latest jicofo does not register to XMPP server as component anymore (due to this commit ref: Remove FocusComponent. (#672) · jitsi/jicofo@49da236 · GitHub ). XMPP component is defined as standard XEP, but I think client_proxy is not.

Would you consider adding jicofo as XMPP component back (at least as an option beside client_proxy)?

Thank you

Sorry, we have bo plans of reverting that code. You can set jicofo jid with the resource in your config.js and you will not need the client_proxy.

Great, thank for your suggested solution!