lazy-loading

Yesterday I decided to improve the way my website loads YouTube videos by only embedding them when a user requests them. Sometimes a page could have as many as 30 videos on, and this would take a long time to load. This is the first time I've attempted a "lazy loading" method of anything, and I figured it would be well worth asking: What can I do to improve on this? How can I make it a bit more graceful? Does this completely miss the point of deferred loading? JSFiddle . Ignore the styling as that's irrelevant here. The way this works is by first placing an anchor on the page containing the

I have found many other posts but they are nt facing exactly the same problem. And they are using a slightly different code. SO I think it is worth reviewing this. I´m using EF6 code first, and I created a Client Entity that has some navigation properties. I´ll post just the relevant code, consider there are a few more properties and foreign keys as well, but not relevant to the problem. Model is generating ok. public class Client { public Client() { JobsExperiences = new Collection<JobsExperience>(); CapacitationCourses = new Collection<CapacitationCourse>(); ScholarLevelDetails = new

I just recently learned about the uses of static local variables in VB.NET and wondered about it's potential use in lazy loading properties. Consider the following example code. Public Class Foo Implements IFoo End Class Public Interface IFoo End Interface Public Class Bar Private _fooImplementation As IFoo Public ReadOnly Property FooImplementation As IFoo Get If _fooImplementation Is Nothing Then _fooImplementation = New Foo Return _fooImplementation End Get End Property End Class This would be a usual, simplified lazy-loading property. You may even want to use the generic Lazy Class to get

I have some large-ish text files that I want to process by grouping its lines. I tried to use the new streaming features, like return FileUtils.readLines(...) .parallelStream() .map(...) .collect(groupingBy(pair -> pair[0])); The problem is that, AFAIK, this generates a Map. Is there any way to have high level code like the one above that generates, for example, a Stream of Entries? UPDATE : What I'm looking for is something like python's itertools.groupby . My files are already sorted (by pair[0]), I just want to load the groups one by one. I already have an iterative solution. I'm just

I usually lazy instantiate my @property objects in their getter methods like this: @interface MyGenericClass : UIViewController @property(nonatomic, readonly) UIImageView *infoImageView // ... @implementation GenericClass - (UIImageView *)infoImageView { if (!_infoImageView) { _infoImageView = [[UIImageView alloc]initWithImage:[UIImage imageNamed:@"PlaceholderInfoImage"]]; } return _infoImageView; } But when subclassing, I would often like to override some of the @properties to be more subclass specific. So I'd like to change the instantiation and do something like: @interface

I have a PrimeFaces p:dataTable and enabled lazy loading by implementing a LazyDataModel . The dataTable holds search results, so when doing a search request the search service only retrieves the required (paginating) data. That works fine. When doing a ajax request with p:commandButton : <p:commandButton id="searchCmdBtn" value="Search" action="#{searchBean.search}" update=":resultForm:resultList :filterForm:filterMenu :resultForm:messages" ajax="true" /> the dataTable gets updated properly, but not the filterMenu in the filterForm (differnt forms, bcz using p:layout ). The filterMenu is one

By definition virtual properties or methods are methods visible to sub classes to be overridden. But, NHibernate for example uses virtual properties to ensure lazy loading. My question is not about NHibernate, but how you could use virtual properties to achieve lazy loading? Are there any hidden behaviors about virtual properties that I don't know? The fact that they are declared virtual allows NHibernate to override the property and create a proxy implementation for it - the proxy in turn they can use to implement lazy loading on the first access of the property. There is no hidden behavior