tag:blogger.com,1999:blog-3367089818389183575.post8300704072060274652..comments2007-08-21T21:31:10.019+02:00Comments on Badlop: XEP33 implementations: separate service or embedded support?badlophttp://www.blogger.com/profile/18298015698267733431noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-3367089818389183575.post-85321647574916118692007-08-21T21:31:00.000+02:002007-08-21T21:31:00.000+02:00Maybe mod_multicast can be used with other Jabber ...Maybe mod_multicast can be used with other Jabber servers using <A HREF="http://www.process-one.net/en/blogs/article/epeios_write_a_module_for_an_xmpp_server_once_run_it_everywhere/" REL="nofollow">Epeios</A>. It is worth investigating.<BR/><BR/>I add this to my TODO list, and will write a blog post with the results of the tests.<BR/><BR/>If I succeed, I'll also write a tutorial in how to get it working with jabberd1 (or the server that I try).badlophttps://www.blogger.com/profile/18298015698267733431noreply@blogger.comtag:blogger.com,1999:blog-3367089818389183575.post-43551182763888784972007-08-21T20:52:00.000+02:002007-08-21T20:52:00.000+02:00Yes, this is problem for more things. I think some...Yes, this is problem for more things. I think some generic protocol for getting special namespace services name from our server. As i can remember, pubsub had big problem in this part also. You dont know where to publish items. Well, pubsub is much more complicated, as there are also receivers who need to get place of published items. Ok, PEP is here for that.<BR/><BR/>But we may need some other services. In client matter, we may need information about proxy65 service for example. It is not problem of server but client, still we need enumerate all services of our server, or in worse case use predefined proxy's from client settings. There is no other automagic way to get jid of service. XEP33 has similar problem, but it needs save more resources as it is server's job. <BR/><BR/>Maybe some hint from server would be good. Some thing like iq:get to="myserver"; give me preffered service jid for xmlns="xep33";<BR/><BR/>server: iq:result from="myserver" jid="multicast.myserver" prio="1" ...<BR/><BR/>I cannot remeber any other protocol using this, but i believe some might use something like it.<BR/><BR/>Anyway, is there way to connect your service to another xmpp server? I thought about making similar service in gloox for generic use, so you can connect to ejabberd, jabberd2, jabberd1.4 or any other with component protocol compatible enough. <BR/><BR/>It used to be all services for jabberd1.4, now everything is only for ejabberd. There are not much external services, i think it should not be too dependent on one implementation.Unknownhttps://www.blogger.com/profile/15741301520855907551noreply@blogger.com