powered by Jive Software

Mulitple connections or JMS client

I saw in a previous thread that an implementation of a messaging (JMS) as a Java client to XMPP would be a nice feature. Has anyone done this?

More importantly, if we have a client that needs to scale to multi connections, which is durable, is it best to use one account per connection, or multiple resources for one account, or is there a better way?

Thanks.

Hey Ahmad ,

I saw in a previous thread that an implementation of

a messaging (JMS) as a Java client to XMPP would be a

nice feature. Has anyone done this?

In fact it would be nice. Unfortunately, I have no references to implementations.

More importantly, if we have a client that needs to

scale to multi connections, which is durable, is it

best to use one account per connection, or multiple

resources for one account, or is there a better way?

This is a nice question. The answer is that it depends on the server implementation since all the work will be done on the server side and not the client side. Being the normal usage one account per connection I guess that most of the server will have that option more optimized than multiple resources for one account. But again, this will depend on the server implementation. So I’'d recommend doing some stress testing on the server if performance is crucial.

Regards,

– Gato

Thanks. I will and will keep this forum informed of my findings…