95965c1dee
keep a parallel implementation of the pin loader to validate the new one
2020-04-07 20:03:41 -04:00
38c1700173
Respond to pinning RPCs as soon as possible
...
(instead of waiting until you've read an unbounded number
of pin logs while queries back up in memory)
Also replace instances of 'publicKey' with 'safeKey' or 'unsafeKey'
to clearly and correctly indicate their format.
2020-02-14 13:46:40 -05:00
cded52f83f
replicate existing pinned.load API correctly
2020-02-14 11:45:51 -05:00
65f88617cf
add support for an optional handler for each pin log
...
great for analyzing which files are most in need of optimization
2020-02-13 18:16:32 -05:00
609eddc9e1
reimplement the the Pinned.load API
...
* recurse into directories on demand
* optimized for lower memory consumption
* less parallelism than before
2020-02-13 17:41:36 -05:00
cd793b295d
provide a standard api for calculating pin data for a given public key
2019-04-17 16:30:45 +02:00
5c9cd5ffc6
standardize pin calculation routine
2019-04-17 14:46:46 +02:00
ansuz