<feed xmlns='http://www.w3.org/2005/Atom'>
<title>pure/docs/research/079-lent-views.md, branch master</title>
<subtitle>Verified execution runtime unifying state, persistence, and replication.
</subtitle>
<id>http://git.yeowoo.org/pure/atom?h=master</id>
<link rel='self' href='http://git.yeowoo.org/pure/atom?h=master'/>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/'/>
<updated>2026-09-27T12:48:55Z</updated>
<entry>
<title>Check pure-serve in Pure, not in aup</title>
<updated>2026-09-27T12:48:55Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-27T12:48:55Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=c08c570d465ffa22c772c2c4d0910eb8a17a379e'/>
<id>urn:sha1:c08c570d465ffa22c772c2c4d0910eb8a17a379e</id>
<content type='text'>
The HTTP host's end-to-end checks (documents against the earlier server,
lending, kill -9 durability, JSON, timers, links, webhooks and answers) sat
in aup's tests, so a change to the host was verified from the toolchain.
They now live in tests/check.py; make check builds their apps with the
sibling aup and runs them after the unit tests, which stay beside their
parts. Design 009 states the rule for all three repositories.

</content>
</entry>
<entry>
<title>Lend a text state's stored extents for its view (079)</title>
<updated>2026-09-26T20:54:49Z</updated>
<author>
<name>eunhhu</name>
<email>necpition205@gmail.com</email>
</author>
<published>2026-09-26T20:54:49Z</published>
<link rel='alternate' type='text/html' href='http://git.yeowoo.org/pure/commit/?id=d693cc750b75b2d862614b6f79f81a311f6294ca'/>
<id>urn:sha1:d693cc750b75b2d862614b6f79f81a311f6294ca</id>
<content type='text'>
A view that shows a text state as it is (pure_module_text_state) now goes
out as the state's stored extents, as a document read does: the answer
holds the store mapping, charged to the budget, until it is sent and its
ticket released; a state with edits not yet stored is copied as before.
Documents and views share one loan path, and the extent array grows as
needed. A 1 MiB note read by 8 connections: 776-817 answers a second
copied, 1,875-1,901 lent, p50 9.2 to 3.5 ms, peak RSS 10.3 to 5.7 MiB.
The load generator learns GET /views/page.

</content>
</entry>
</feed>
