Ah, I misspoke. What I meant by "bad idea" was that having N
FetcherThreads calling one RegexURLFilter may negate the performance
gain of doing the filtering inside FetcherThread. So it's not bad as
in "go boom", just "go slow".
(RegexURLFilter.filter() is already synchronized; URLFilter.filter() is not.)
--matt
On Thu, 06 Jan 2005 13:50:34 -0800, Doug Cutting <
cutting@nutc...> wrote:
> Matt Kangas wrote:
> > One issue with my code is that I use URLFilter, but expect the filter
> > to be thread-safe. A naive user might be tempted to use RegexURLFilter
> > at this filter-point, which is a bad idea.
>
> Sounds like we should add some synchronization to RegexURLFilter...
>
> Doug
>
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....
http://www.thinkgeek.com/sfshirt
_______________________________________________
Nutch-developers mailing list
Nutch-developers@list...
https://lists.sourceforge.net/lists/listinfo/nutch-developers
opensubscriber is not affiliated with the authors of this message nor responsible for its content.