We are NOT writing a browser (that needs to always display the whole content in the end), we're writing a RESTful API.
Should you be writing a browser, you could use the API and implement the "eager loading" or, more precisely "eager
rendering" on top of it.
Similarly, if you shoot for some speculative performance improvements based on the partial cached data, you should be
able to implement it on top of the API. At least for now. Once such solution matures, we can consider putting into the
API. For now, being able to conveniently add links on the server side and conveniently follow them on the client side is
a good start IMO.
Over and out,
Marek
On 08/04/2011 08:16 PM, Markus KARG wrote:
> Even if we do not vote for eager loading as nobody but me seems to
> see the benefit (BTW, Google just posted that their next Chrome will do
> exactly that and even pre-render!)