> From: André Warnier [mailto:[EMAIL PROTECTED]
> Maybe hacks, but why not use them if they are easier, faster,
> and have a smaller memory footprint ?
Because they can be harder to maintain. Note *can be* - it depends on the
developers and admins.
> Not being very good at either Java or Tomcat, I'll submit the
> following
> ideas, and watch for comments :
>
> Depending on what exactly you need to pass as information,
> why not just
> the fact of whether a given "flag" file exists in a directory under
> catalina.base ? I know that this sounds quite pedestrian, but
> considering that a webserver already makes zillions of file accesses
> anyway, I don't think the overhead of a few more would matter.
>
> Or, if both webapps already use some common database, a
> record in ditto
> database. That is probably more flexible and more reliable re locking.
>
> Or, a webapp with the appropriate permissions can set/reset/read a
> system property, and these should be shared by all apps under the same
> JVM instance, no ? what I don't know is if set/reset of a system
> property is "atomic".
I think the OP wanted webapp A to call webapp B and return the result from B,
via A, to the user. None of these cause A to invoke code in B, though they're
all solutions to the problem of A informing B that something has changed.
- Peter
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
