Summary

In this chapter, we covered a lot of information about load(). We first discussed how it can be done only in the client and then moved on to some finer details about how it works. After that, we looked at using load() in layouts to minimize the number of requests made for each page load and maximize convenient access to data that may be needed application-wide. We also looked at invalidating data in cases where we would want data to be reloaded. Finally, we covered how server load() functions are called by RequestEvent, which gives us access to so much more valuable information. That information can enable us to build cookie-based login functionality for our application.

Having spent this chapter learning about some of the finer details behind load(), you should feel comfortable taking a load off and relaxing. If you have any baked cookies to hand, I suggest you take a break from the book and treat yourself to some. You’ve earned it.

But do come back because, in...