Messaging module implementation

Installation
1

Hi,
I need to know how messaging module has been implemented on server side. Can somebody please answer the below Qs

  1. Is it comet based?
  2. Is it a blocking or non blocking implementation? (blocking the thread or not)
  3. What is the number of parallel client connections that a tomcat server deployment would support?

Thanks,
Ankur

2

It’s Comet-based, blocking, and the number of threads depends on your exact hardware and operating system and the surrounding netwokr environment more than anything else.

If you’re interested in a non-blocking implementation based on Jetty’s continuations (or similar not-yet-standardized features in other engines), that’s a feature that could be sponsored.

3

Is messaging module based on polling?

Can you please clarify if the messaging module is based on polling or not? The deployment i have keeps on making server calls at a fixed interval. Is there a way to configure how many server calls per time interval?

Also, it would be great if you can provide some flow/sequence diagrams or any other documentation that explains the working of messaging module.

Thanks,
Ankur

4

One again, it’s Comet-based, which means it does not use polling. However it will re-establish the HTTP streaming connection every two minutes by default, because intervening firewalls and proxies are often configured to sever connections that last longer than that.