[ejabberd] problem with external components
stpeter at stpeter.im
Fri Jun 13 18:48:53 MSD 2008
On 06/13/2008 3:30 AM, Fabio Forno wrote:
> On Fri, Jun 13, 2008 at 11:08 AM, Pedro Melo <melo at simplicidade.org> wrote:
>> hmms... Our components just work with ejabberd, and on previous
>> servers I've used the answer <stream> was always from server domain.
>> I think this might by a typo in the spec. It does not make much sense
>> to have a from='component.domain'...
> It's possible (in fact at the beginning I wasn't understating the
> problem, since I expected a bare "domain" from), but at least openfire
> and the jabber support in twisted matrix are compliant to the typo ;)
IIRC, this is an oddity in the original jabber component protocol (not a
spec typo but a protocol "feature"). Clearly we need to finish work on
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7338 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.jabber.ru/pipermail/ejabberd/attachments/20080613/8a43e858/attachment-0001.bin
More information about the ejabberd