lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Erik Hatcher <>
Subject Re: ValueListHandler pattern with Lucene
Date Fri, 09 Apr 2004 20:18:41 GMT
Patterns are work-arounds for language deficiences :)

Don't use patterns because some book said so - use them if they are the 
pragmatic choice.  Flattening data for reports or search results and 
perhaps being a little more coupled to Lucene between tiers in order to 
avoid performance problems seems a wise way to approach it.  Or go 
straight to Lucene from the presentation tier - no one said you had to 
proxy it through some other layer.

I would highly recommend *against* loading all documents from a search 
into a collection and passing it across tiers - you're only asking for 


On Apr 9, 2004, at 4:06 PM, wrote:

> On Friday 09 April 2004 21:30, Erik Hatcher wrote:
>> Do you really need *all* documents from Hits?  If not, then you should
> Only the user knows ;-) Well, no, I very likely only need one or a few 
> but
> nevertheless I have to pull all hit results to the presentation tier...
> That's just the problem. Using a VLH I have to fetch all hits from the 
> Hits
> instance and put them into the VLH - ordinarily you would lazily only 
> fetch
> the hits you actually need them - at the time you need them.
> That's just my question :-)
> So, to repeat, my idea was to use a wrapper for the VOs in order to 
> fetch only
> some hits at a time...
> It's actually a VLH pattern drawback. Maybe I should ask the blueprint
> people ;-)
> Timo
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message