2025-05-08T17:51:32Z

Dorian Taylor

Even once caching is implemented, a full server round-trip for the whole page with every POST is costly and often unnecessary.

Even ordinary page GETs when the graph state has not changed can be slow, particularly the first time a user loads a generated resource.

Finish implementing addressable transforms.

How are we going to handle cache entity bodies?

How are we going to represent the metadata for the cache entries?

Implement caching of generated representations against Store::Digest.

Implement internal caching.

Intertwingler currently lacks any internal caching, so I don't trust it standing up to even the baseline thrash of the open internet.

Intertwingler MVP

It is possible for two different requests to produce the same cache entity.

Sense Atlas Front End

The two most robust solutions for speeding up Sense Atlas (plus the visualization layout) are also each fairly significant subprojects.

We were relying on browser cache to keep XSLT from being intolerably slow.

We will need to be able to handle a much higher request rate if we expose Intertwingler to the open internet.