diff options
| author | jrayhawk <jrayhawk@web> | 2009-09-17 15:06:17 -0700 |
|---|---|---|
| committer | piny-code <ikiwiki-piny-code@piny.svcs.cs.pdx.edu> | 2009-09-17 15:06:17 -0700 |
| commit | 5cb17a0bc2a13e1e7b019b270c7bb586d28f9557 (patch) | |
| tree | 70295164c207281e91a7c9d1613fa44a3251a359 /architecture | |
| parent | 772f39d863e8dec8ec5ea444768f32f3eeb21120 (diff) | |
| download | piny-code-5cb17a0bc2a13e1e7b019b270c7bb586d28f9557.tar.gz piny-code-5cb17a0bc2a13e1e7b019b270c7bb586d28f9557.zip | |
Adding note on caching.
Diffstat (limited to 'architecture')
| -rw-r--r-- | architecture/data.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/architecture/data.mdwn b/architecture/data.mdwn index fa83ca9..ce951e0 100644 --- a/architecture/data.mdwn +++ b/architecture/data.mdwn @@ -1,6 +1,6 @@ Data model! -Dynamic data lookup should opportunisticly cache any associated cheap data. For instance, there are three data from stat(/srv/git/$reponame.git), so looking up one should grab the others. /etc/password parsing would be similar. +Dynamic data lookup should opportunisticly cache any associated cheap data. For instance, there are three data from stat(/srv/git/$reponame.git), so looking up one should grab the others. Jules points out that everything here is inherently cached, and I should be using getpw*() for passwd parsing. [[!table format=dsv delimiter=# data=""" datum #stored location #constraint |