[Owasp-appsensor-project] Filter HashMaps and Thread Safety
jtmelton at gmail.com
Fri Aug 5 08:39:42 EDT 2011
I'm the lead dev, but am on vacation at the moment. I'll take care of these
when I get back next week sometime.
On Thu, Aug 4, 2011 at 9:52 PM, Owen Berger <owen.k.berger at gmail.com> wrote:
> This is my first time on the appsensor list, so please let me know if my
> questions have been asked before and I missed it.
Welcome - glad you're looking into it. If you want to [and are able] to
share your use case, please do - we're interested in gathering info about
how folks are using appsensor.
> -What is the best way to implement a thread-safe version of the Static
> HashMap used in the User Agent and Client IP filters?
I updated the codebase recently to use concurrenthashmaps but I might have
missed these places. I'll look when I get back from vacation.
> -Are the Maps thread-safe as is, e.g. as Static maps inside the filter, or
> would a singleton using a ConcurrentHashMap do the same or better job for a
> web application where state is needed?
These are not thread-safe as is as you mention. They were very simple
examples as you can see, so are not "production" quality. If you end up
making useful changes, please feel free to share back and we can improve
> -I would like to make the maps subject to a cleaner that removes all of the
> old map entries utilizing a Job in Quartz, so is that still possible in the
> filter if I use the Static HashMap?
I've thought a bit about your point of the "cleansing" routine. I don't
think it would work well in it's current incarnation, but you should be able
to move it out to a context style object, make it thread safe and then
access it from both the filter and your quartz job.
> Thanks for any help or direction,
> Owasp-appsensor-project mailing list
> Owasp-appsensor-project at lists.owasp.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Owasp-appsensor-project