-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jackose,
On 6/4/2009 9:07 AM, Jackose wrote: > Say for example, I have four clients and a server. If client1 sends the > message "hi", the server receives the message "hi" and the server must send > this "hi" message to clients1,2,3 & 4. This isn't really how HTTP works. The clients always initiate the requests, and the server fulfills them. Any web-based services that appear to work otherwise are doing one of the following: 1. Clients are polling the server for messages (resource-intensive). (Think gmail) or 2. Clients are themselves acting as servers, and the "server" is acting as a client. (Think web services) There are some semi-standard ways to send messages like this using publish/subscribe capabilities. Two such strategies that come to mind are MQ (aka Java Message Service which is pub/sub using #2 above) and RSS (which is polling a la #1 above). - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkooPBEACgkQ9CaO5/Lv0PBwWgCgu6JVxMqUfxQt7QpCM1LGfPIX 0isAn0hzsDXoPdEfjDOwu3nxHPOky3Vy =+Iuw -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
