 Andrew Pendleton
|
4bbfaf9919
|
Bump to v0.9.0
|
2016-04-15 13:26:06 -04:00 |
|
|
Andrew Pendleton
|
405d987716
|
Ditch inflateSync in favor of plain inflate; test iteration order; add d3-queue dep
|
2016-04-14 18:49:34 -04:00 |
|
|
Andrew Pendleton
|
4474634452
|
Improve error handling for geocoderDataIterator
|
2016-04-14 13:32:38 -04:00 |
|
|
Andrew Pendleton
|
d3845ea9f9
|
Add test of geocoderDataIterator
|
2016-04-14 13:24:27 -04:00 |
|
|
Andrew Pendleton
|
b6ef79d7dc
|
I give up: setImmediate for every callback
|
2016-04-04 13:16:52 -04:00 |
|
|
Andrew Pendleton
|
b37655577f
|
Increase the frequency of calling setImmediate in the geocoderDataIterator function
|
2016-04-04 10:49:34 -04:00 |
|
|
Andrew Pendleton
|
11b6381c4f
|
Another attempt at avoiding overflowing the callstack on geocoderDataIterator: every tenth time we call a callback, call it via setImmediate to reset the stack
|
2016-04-01 01:16:01 -04:00 |
|
|
Andrew Pendleton
|
3967adcb4a
|
Avoid callstack loop by making sure only one geocoder data iterator buffer-flush operation is happening at once
|
2016-03-30 01:10:20 -04:00 |
|
|
Andrew Pendleton
|
aac15a8f81
|
Ditch geocoderDataForEach (it's a memory hog) and instead go with an async iterator method with an internal buffer, implemented around sqlite limits, to give caller more control over reads
|
2016-03-17 17:55:34 -04:00 |
|
|
Andrew Pendleton
|
3c7f5c8462
|
And infrastructure for iterating over geocoder data
|
2016-03-05 17:12:17 -05:00 |
|