Batched fetching

[petehunt]

If I nest a Person inside of a Movie, there are going to be 2 serial fetches (which discourages composition due to the perf hit).

Instead, if getDataUrl() were a static function of the route (rather than an instance method of the props) it could be called recursively before the components are rendered so you can fetch all of the data you need to.

[ovidiuch]

Interesting idea. It would be even cooler if the API could support more than one request in a HTTP connection (something like django-superbulk).

But I'm not sure how you can trace all the components to be loaded all the way from the root component to the tree leaves. The component props can either come from an already fetched and parsed request or from the DOM, which is hardcoded inside the render method.

[ovidiuch]

A similar but reversed idea that I've been thinking about is for generateSnapshot to nest all the composed component props recursively. This has two benefits. 1. You can persist the entire state of a component including its children and it all will be loaded without the need of any request. 2. The cached history entry will also contain the entire nested props/state which will again render all the current hierarchy of components in a blink when going back in history.

[ovidiuch]

As honored as I am for having an issue opened by @petehunt, this is no longer relevant as the Cosmos project evolved into something that supports React components instead of dictating their design (besides the need to be encapsulated).

Pete–whatever you may be doing at the moment, if you ever get another chance to check out the new project mission feel free to check out the (simplified) README: https://github.com/skidding/cosmos/blob/master/README.md