You can do pretty much anything you want to. The question is more: what are your requirements? Since you want to break the request-response protocol that is HTTP, can you chuck the web app completely and go two-way RMI? That would probably be the simplest and cleanest implementation. HTTP client->server and RMI server->client would be clunky but would preserve your original architecture. Of course, if you have firewalls to deal with, it may not be an option. There's a lot of publish-subscribe messaging solutions out there. They are particularly good for connecting disparate systems, but you may be able to use one for your purpose. But again, firewalls bring them to a screeching halt. The solution depends on what your situation is. [ January 28, 2004: Message edited by: Joe Ess ]
