Does anyone know of a c++/c framework/API for developing JEP-0114 external components for Jabber servers? Also should it be possible to develop an external component that replaces the built in server to server module in openfire, as in does that interface support that use?
Hey edify,
Does anyone know of a c++/c framework/API for developing JEP-0114 external components for Jabber servers?
In the components list you can find the Jabber Component Runtime. That library/tool was developed for jabberd14 but if it follows the XEP-114 spec then it should work with Openfire. You can also check the list of libraries to see if one of them has support for XEP-114 in C/C++.
Also should it be possible to develop an external component that replaces the built in server to server module in openfire, as in does that interface support that use?
Components provide new services to a server. In the case of Openfire, new services are represented as new subdomains under the hosted XMPP domain. For instance, if you server’'s domain is myserver.com then new components will be of the form [myservice].myserver.com. That is the main reason why components cannot replace the s2s logic built into the server. Anyway, I would be curious to learn why would you need to do that.
Regards,
– Gato
The reason I’'d like to do it is:
http://www.igniterealtime.org/forum/thread.jspa?messageID=144776𣖈
Hey edify,
Already replied on that thread regarding your other question.
Regards,
– Gato