[rabbitmq-discuss] Rabbitmq-xmpp patches and the future.

[Alexis Richardson]

Eric

Thank-you.  Should we recommend this from the XMPP section of our web site?

alexis

On Wed, Dec 15, 2010 at 1:13 PM, Eric Liang <eric.l.2046 at gmail.com> wrote:
> On 12/15/2010 05:38 PM, Alexis Richardson wrote:
>> Eric
>>
>> Nice work!
>>
>> Please do tell us more about this.
> Thanks Alexis for your attention.
>
> What I've done to the project have been already added to the text file
> in the repository: README.CUSTOMIZED. As it might be too brief for you,
> I'd like to explain some details in the following.
>
> I've separated the initial modules to four individual ones, and the main
> purpose is to index the codes by module. That is, the initial module (
> mod_rabbitmq ) will communicate with the xmpp clients and route the
> consume-related requests to the consumer processes, while all the
> functions about how to consume are implemented in the consumer module (
> mod_rabbitmq_consumer ). As these two modules will directly communicate
> with the rabbitmq-node, some utility functions are distilled to an
> individual module ( mod_rabbitmq_util ). To reduce the calls in function
> like basic_consume, the mod_rabbitmq_util module will load a library to
> the rabbitmq-node , and this is why the mod_rabbitmq_util_priv module is
> designed.
>
> Meanwhile,  a heartbeat check on the rabbitmq-node is added, which will
> print error message when retrying to connect and grab the latest
> rabbitmq-node configuration in ejabberd if the retry times overflowed a
> default setting (5). The check on the connection is simply a ping
> action. And once the rabbitmq-node was updated when retrying, it will
> broadcast the change to all of the consumer processes, since the node
> configuration is stored in the process data.
>
> That's all I can think of it for now. Please do not hesitate to contact
> me if any further information was required.
>
> Thanks,
> Eric
>
>> On Wed, Dec 15, 2010 at 3:02 AM, Eric Liang <eric.l.2046 at gmail.com> wrote:
>>> Hi all,
>>>
>>> I've done some patches for rabbitmq-xmpp recently, which was released by
>>> Tony Garnock-Jones (
>>> http://www.lshift.net/blog/2008/07/01/rabbitmq-xmpp-gateway-released ).
>>> The patches have been posted to github (
>>> https://github.com/ericliang/rabbitmq-xmpp ). I've contacted Tony and he
>>> has no time to check these patches right now and suggested that
>>> I get in touch with the list ( thanks Tony for your attention and those
>>> enlightening conversations ).  So would anyone here like to test/review
>>> these patches and/or to merge them to the official repository if
>>> valuable? Thanks in advance.
>>>
>>> By the way, as Tony suggested and we reach an agreement on the future
>>> version of rabbitmq-xmpp, which the service should be a plugin as
>>> rabbitmq-stomp and communicate with the ejabberd server with the help of
>>> an xmpp client library. And in that case, the Rabbit team should be the
>>> best one to do that I guess. Anyway, if there is no roadmap for it or
>>> the future, this would be a suggestion and I'd like to do more work on
>>> it when necessary.  Would you mind to tell something about this?
>>>
>>> Thanks for your attention and any other suggestions are appreciated.
>>> Eric
>>>
>>> --
>>> -----BEGIN GEEK CODE BLOCK-----
>>> Version: 3.1
>>> GCM/CS/E/MU/P d+(-) s: a- C++ UL$ P+>++ L++ E++ W++ N+ o+>++ K+++ w !O
>>> M-(+) V-- PS+ PE+ Y+ PGP++ t? 5? X? R+>* tv@ b++++ DI-- D G++ e++>+++@ h*
>>> r !y+
>>> ------END GEEK CODE BLOCK------
>>>
>>> _______________________________________________
>>> rabbitmq-discuss mailing list
>>> rabbitmq-discuss at lists.rabbitmq.com
>>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>>
>
>
> --
> -----BEGIN GEEK CODE BLOCK-----
> Version: 3.1
> GCM/CS/E/MU/P d+(-) s: a- C++ UL$ P+>++ L++ E++ W++ N+ o+>++ K+++ w !O
> M-(+) V-- PS+ PE+ Y+ PGP++ t? 5? X? R+>* tv@ b++++ DI-- D G++ e++>+++@ h*
> r !y+
> ------END GEEK CODE BLOCK------
>
>