;
> iEYEARECAAYFAkmsFQIACgkQ9CaO5/Lv0PC2mACdEmW+hq/u2W+jY7kgr9Md4Qhm
> dBQAnRxW3YE+wsbX3Nabkauk513AtYpc
> =DXBg
> -END PGP SIGNATURE-
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
--
Regards,
Edward Song
Java Web Developer
631-396-5000 x306
Hi all,
Just soliciting some feedback on how to effectively, thwart data mining on
our server.
We have a reactive solution when it comes to screen scraping and data mining
on Tomcat 5.5.
We simply find the offending IP's and add them to the deny rules using the
Valve - org.apache.catali
I believe it is because you are sharing the class definition, not instances,
even if they are static instances.
So webapp1 will create a static instance of Sharer, so will webapp2 off of
the same class definition, but each will have its own instance.
-Original Message-
From: java_is_ever
"common" folder?
To: Tomcat Users List
Send reply to: Tomcat Users List
> Steve Ochani wrote:
> > On 9 Jul 2008 at 11:57, Edward Song wrote:
> >
> >
> >> What are the consequences of putting shared web resources in t
What are the consequences of putting shared web resources in the "common"
folder vs. the "shared" folder?
I'm not sure how to articulate the consequences of putting shared resources
in the "common" folder.
The following below is in the documentation, but is it enough to force
another QA cycl
