-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Darryl,
Darryl Pentz wrote: > 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. What are your options for simply moving the "webapp B" processing into "webapp A"? Do you have any? I think it might help if we had an example of what you're actually doing. If you can't give us details, how about generalities like "I might have to invoke a JSP" or "I have a specific servet that needs to be called" or "this isn't really HTTP at all". What I find to be the "KISSiest" (thanks Leon) approach is for your application to "drink its own Kool-Aid" by using the same interface that the rest of the world would see for whatever application B (which almost sounds like a service) would see. I hope that stimulates some discussion. With this crowd, if no doubt will. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjvsCUACgkQ9CaO5/Lv0PBckgCePZEUkp8Q7fpmwbALtmp02lXK sVUAoKR/ivY54UGpe6mycTDXTdH6zNtz =ng4l -----END PGP SIGNATURE----- --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
