lazy-loading

I have the following code which could be called via multiple web-requests at the same second. As such, I don't want the second+ request hitting the database, but waiting until the first one does. Should I refactor this to use the Lazy<T> keyword class instead? If 10 calls to a Lazy<T> piece of code occur at the same time, do 9 of those calls wait for the first one to complete? public class ThemeService : IThemeService { private static readonly object SyncLock = new object(); private static IList<Theme> _themes; private readonly IRepository<Theme> _themeRepository; <snip snip snip> #region

Assuming I have a select like this: <select size="4"> <option id="1">Please wait ...</option> <option id="2">Please wait ...</option> <option id="3">Please wait ...</option> <option id="4">Please wait ...</option> <option id="5">Please wait ...</option> </select> I should see a List of 4 elements having a scrollbar on the right. What i like to do now is to load the text via ajax if the option becomes visible somehow (scrolling and/or initial). EDIT: At the end, I do not load them lazy because of the huge metadata transfer. This is the request I must upload (send to the server): This is

I have a few entities with lazy one to many relationships (logic omitted for brevity): @Entity class A{ @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinColumn(name = "a_pk", nullable = false) List<B> blist = new ArrayList<>(); @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinColumn(name = "a_pk", nullable = false) List<C> clist = new ArrayList<>(); @Column(name = "natural_identifier", nullable = false) private String id; } @Entity class B{ } @Entity class C{ @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinColumn(name = "c_pk", nullable =

Lazy loading is a commonly used technique. However, in Angular it seems that the granularity level of this technique stops at the module level. That means that you can have module main that loads in the browser, and then on special occasion module B and C and D can be loaded lazily. Almost all tutorials on web explain that. However, is there a way to load components lazily? Consider this simple example that user goes inside the application, and when clicks "invoices" link, URL changes to the new route /invoice/list and a progress bar shows loading, while the invoices component including HTML

I have a document generator which contains queries for about 200 items at the moment but will likely be upwards of 500 when complete. I've recently noticed that some of the mappings denote lazy loading. This presents a problem for the document generator as it needs access to all of these properties based on which document is being generated. While I am aware of the DataLoadOptions that can be specified to the context, this would result in me having to explicitly specify every column that could possibly be loaded. That is north of 1000 as it all of the data fetching takes place in one context.

I am fetching a lot of thumbnails in my application from a remote server and lazy-loading these in a list view. The image fetches run in a background AsynTask and when completed the fetched images are stored in a HashMap using SoftReferences. This works just fine but when the images in the cache gets GC’d, the fetches have to be rerun. I could have stored them on the SD card so there would be no re-fetching. But I did not take this approach because of the clutter it would create on the SD card. Are there perhaps alternatives to these sorta like temporary folders that can be cleared when