I always find this annotation as misleading. It tightens the current
habbit of tightly binding services with servers.
Yeah, that's the main thing about it that bothered me. The standards
seem to encourage the use of sub-domains for naming services. The
examples in XEP-0030 place each service on a
Hi Keith,
I did some investigations on this topic last year. As far as I see it is
not possible without rewriting the sm-component to pass some iq-stanzas
to its clients.
My approach was to write a component that binds to a dummy-domain and
simulates a c2s-connection (e.g. the component starts a
Dnia 2011-01-31, pon o godzinie 23:23 -0800, Keith Jay Gillis pisze:
A host that offers text-based conferencing capabilities; often but not
necessarily a sub-domain of a Jabber server (e.g.,
conference.jabber.org).
I always find this annotation as misleading.
It tightens the current habbit of
Hi,
XEP-0045 defines a multi-user chat service as:
A host that offers text-based conferencing capabilities; often but not
necessarily a sub-domain of a Jabber server (e.g.,
conference.jabber.org).
Is it possible to use mu-conference with jabberd2 without putting
mu-conference on a sub-domain?
