I'd also add that the Document keeps a pointer to the spot in storage where that value can be loaded from. It can result in a performance saving in the typical search use case where one is displaying just "metadata" fields on a page, but not the full content. In this case, the full content page is loaded lazily while the smaller metadata fields are loaded as usual.
-Grant On May 24, 2010, at 12:15 AM, Shaun Senecal wrote: > When a field is lazy loaded, the actual value is not retrieved from > the server until it is rendered by the UI. This is the same behaviour > as the LiveView that ExtGWT currently supports. The difference is > that once a value has been retrieved once, LazyLoad will not fetch > that value from the server again. LiveView will request the same > values over and over again as the user scrolls up and down. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org > For additional commands, e-mail: java-user-h...@lucene.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
