In my case, webapp A needs to let webapp B know that an event has occurred ...
webapp B then does something based on that event, and the result of that action
is relevant to webapp A.
I did in fact use HttpURLConnection because the original HttpClient class
(Commons I think) was a memory pig and just turned out to be way too
inefficient. I don't involve any JSP's. Webapp B has a simple EventServlet that
gets the request from webapp B.
I guess in answer to your KISS comment, the thought of being able to do
something inside the VM, as opposed to the overhead of opening up a socket and
doing the comms, just seems heavy and I do seem to have varying performance
with my HTTP approach that I can't seem to isolate. Admittedly I am using
Groovy on the webappA side, but that shouldn't impact performance to the extent
I'm seeing.
I appreciate the suggestions from all so far. It does seem like at least there
isn't a 'no-brainer' approach, as in "of course stupid, why don't you just do X
- everybody else does". It sounds like each solution has its clear pros and
cons which must be weighed up in light of my particular environment and
requirements.
- Darryl
----- Original Message ----
From: Mikolaj Rydzewski <[EMAIL PROTECTED]>
To: Tomcat Users List <users@tomcat.apache.org>
Sent: Wednesday, October 8, 2008 12:54:10 PM
Subject: Re: Communicating between webapps
Leon Rosenberg wrote:
> You need additional lib (commons httpclient), you need special
> servlet/action/jsp on B-side, you probably need to start threads, you
> need to monitor those on A side, and and and...
>
One can use HttpURLConnection. There're probably some actions/jsps
already in the webapp, one more makes no harm.
Anyway, yes, it's maybe more work than to extend Remote. But IMO gives
you more flexibility than RMI. It's easier and more common to allow HTTP
trafic through firewalls, than RMI traffic.
We don't know what kind of infromation Daryl wants to exchange. Maybe
it's worth to go with RMI, maybe it isn't.
--
Mikolaj Rydzewski <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
