00:12:04  * mikealjoined
00:24:35  * fritzyjoined
00:32:00  * ednapiranhaquit (Quit: Leaving...)
00:34:41  * fritzyquit (Remote host closed the connection)
00:46:39  * brianloveswordsjoined
00:58:51  * kid_icarusquit (Quit: Leaving)
01:02:58  * wangbusjoined
01:07:11  * brianloveswordsquit (Quit: Computer has gone to sleep.)
01:39:37  * brianloveswordsjoined
01:39:51  * neonstalwartjoined
01:45:01  * neonstalwartquit (Quit: Leaving.)
01:58:49  * kid_icarusjoined
02:16:10  * ednapiranhajoined
02:36:40  * domanicjoined
02:53:12  * brianloveswordsquit (Quit: Computer has gone to sleep.)
03:03:45  * brianloveswordsjoined
03:08:38  * mikealquit (Quit: Leaving.)
03:10:02  * brianloveswordsquit (Quit: ["Textual IRC Client: www.textualapp.com"])
03:13:53  * brianloveswordsjoined
03:25:47  * ednapiranhaquit
03:26:31  <wangbus>need some guidance on design. anyone have some time to help?
03:41:04  * brianloveswordsquit (Quit: Computer has gone to sleep.)
03:44:54  <wangbus>oh well here goes. for things like counts, statistics that need to be updated on each put
03:45:10  <wangbus>they would need to be atomic i'm guessing
03:45:21  <wangbus>not sure how to design this or if it is even the right place to do it.
03:46:21  <wangbus>using a sublevel and noticed substack's locking module and dominic tarr's trigger liv
03:46:25  <wangbus>lib*
03:46:43  <wangbus>not really sure what is the best usage, but at a high level what i'm looking for is atomicity
03:46:47  * kid_icarusquit (Quit: Leaving)
03:46:52  * mikealjoined
03:56:39  * thlorenzquit (Remote host closed the connection)
04:09:22  <substack>wangbus: when the app loads, pull the counter from level (and don't let any requests go through until it's loaded)
04:09:42  <substack>then keep the counter in memory and batch the counter updates with each PUT
04:10:14  <substack>either explicitly if you only need to put in a few places or more implicitly with level-trigger
04:11:09  <substack>it's a little tricky since you need to wait for each PUT to finish before you can safely increment the counter in memory
04:22:43  * mikealquit (Quit: Leaving.)
04:31:53  * mikealjoined
04:44:38  * fritzyjoined
04:45:13  * mikealquit (Quit: Leaving.)
04:52:07  * dguttmanquit (Quit: dguttman)
04:52:17  * mikealjoined
04:52:48  * dguttmanjoined
05:18:50  * domanicquit (Ping timeout: 260 seconds)
05:59:07  * dmuellerjoined
05:59:47  * mcollinajoined
06:09:25  * dmuellerquit (Quit: sleeping, who needs sleep?)
06:15:45  * fritzyquit (Remote host closed the connection)
06:16:03  * fritzyjoined
06:16:30  * fritzyquit (Remote host closed the connection)
06:51:53  * mcollinaquit (Remote host closed the connection)
06:54:36  * mcollina_joined
07:22:05  * timoxleyjoined
07:32:01  * fritzyjoined
07:37:05  * fritzyquit (Ping timeout: 244 seconds)
07:45:01  * fritzyjoined
07:49:40  * fritzyquit (Ping timeout: 250 seconds)
08:26:49  * stagasjoined
08:34:01  * wilmoorejoined
10:25:15  <wangbus>substack: interesting. thanks for the insight. will try.
10:46:11  * stagasquit (Ping timeout: 244 seconds)
11:14:21  * mcollina_quit (Remote host closed the connection)
11:15:01  * mcollinajoined
11:19:03  * mcollinaquit (Ping timeout: 240 seconds)
11:45:41  * mcollinajoined
11:51:03  * mcollinaquit (Ping timeout: 240 seconds)
11:56:11  * mcollinajoined
12:35:12  * ramitosquit (Remote host closed the connection)
12:35:45  * ramitosjoined
13:14:33  * ramitosquit (*.net *.split)
13:14:33  * prettyrobotsquit (*.net *.split)
13:14:33  * ggreerquit (*.net *.split)
13:14:34  * jaynequit (*.net *.split)
13:15:34  * ramitosjoined
13:15:34  * prettyrobotsjoined
13:15:34  * ggreerjoined
13:15:34  * jaynejoined
13:42:06  * thlorenzjoined
14:03:18  * neonstalwartjoined
14:13:30  * Ariaquit (Ping timeout: 250 seconds)
14:21:33  * aredrideljoined
14:37:16  * jjmalinajoined
14:44:48  * brianloveswordsjoined
14:46:20  * jerrysvjoined
15:01:19  * kevinswiberjoined
15:01:26  * kevinswiberquit (Remote host closed the connection)
15:01:42  * kevinswiberjoined
15:02:36  * ednapiranhajoined
15:16:24  * mikealquit (Quit: Leaving.)
15:17:49  * fritzyjoined
15:23:08  * kevinswiberquit (Remote host closed the connection)
15:23:41  * kevinswiberjoined
15:28:01  * kevinswiberquit (Ping timeout: 255 seconds)
15:29:37  * domanicjoined
15:32:21  * kevinswiberjoined
15:32:53  * fritzyquit (Remote host closed the connection)
15:36:00  * domanicquit (Ping timeout: 255 seconds)
15:37:03  * domanicjoined
15:44:47  * domanicquit (Ping timeout: 245 seconds)
15:47:31  * blessYahu_quit (Ping timeout: 256 seconds)
15:47:51  * fritzyjoined
15:50:50  * jerrysvquit (Remote host closed the connection)
15:51:25  * jerrysvjoined
15:51:46  * mikealjoined
15:56:53  * fritzyquit (Read error: Connection reset by peer)
15:57:14  * domanicjoined
15:57:14  * fritzyjoined
16:04:16  * fritzyquit (Remote host closed the connection)
16:05:58  * fritzyjoined
16:09:37  * domanicquit (Ping timeout: 256 seconds)
16:15:51  * dmuellerjoined
16:16:03  * wilmoorequit (Ping timeout: 255 seconds)
16:32:26  * neonstalwartquit (Read error: Connection reset by peer)
16:32:48  * neonstalwartjoined
16:32:52  * fritzyquit (Read error: Connection reset by peer)
16:33:22  * fritzyjoined
16:45:56  * thlorenzquit (Remote host closed the connection)
16:58:05  * wilmoorejoined
16:58:05  * fritzyquit (Read error: Connection reset by peer)
16:58:30  * fritzyjoined
16:59:19  * dmuellerquit (Quit: sleeping, who needs sleep?)
17:05:36  * aredridelchanged nick to Aria
17:07:15  * stagasjoined
17:07:20  * kid_icarusjoined
17:10:16  * fritzyquit (Remote host closed the connection)
17:17:03  * kevinswiberquit (Remote host closed the connection)
17:19:06  * domanicjoined
17:29:24  * dmuellerjoined
17:50:00  * fritzyjoined
17:57:02  * mcavagejoined
18:31:33  * kevinswiberjoined
18:36:12  * wilmoorequit (Ping timeout: 250 seconds)
18:54:06  * domanicquit (Ping timeout: 260 seconds)
18:55:26  * mikealquit (Quit: Leaving.)
18:55:36  * mikealjoined
18:56:05  * wilmoorejoined
18:56:56  <neonstalwart>what would be the most efficient way to skip the first n items? is it just using a readStream piped to through with a write that will ignore the first n-1 items?
18:57:41  <neonstalwart>actually… it would ignore the first n items (since i want to skip the first n items)
19:45:17  <nolanlawson>neonstalwart: unfortunately, that's the fastest way
19:45:40  <nolanlawson>it's kind of how leveldb/indexeddb were designed; there's no fast way to start at a particular offset
19:46:48  <neonstalwart>nolanlawson: thanks - i was wondering about doing just a keyStream but then realized that my needs are that i need to skip the first n items that match some criteria so i need the values too to see if each value counts as one that i've skipped or not.
19:47:32  <neonstalwart>i thought that the keys alone might somehow be a bit faster but, as i said, that doesn't give me what i need in this case so it's not something to even wonder about :)
19:50:31  <nolanlawson>typically anything you can do with limit/offset you can do with limit/startkey instead
19:51:13  <neonstalwart>yeah, i'm building something to match an existing API that is limit, offset
20:05:54  * neonstalwartquit (Quit: Leaving.)
20:11:52  * kevinswiberquit (Remote host closed the connection)
20:12:26  * kevinswiberjoined
20:13:52  * stagasquit (Ping timeout: 240 seconds)
20:16:44  * kevinswiberquit (Ping timeout: 250 seconds)
21:40:50  * brianloveswordsquit (Quit: Computer has gone to sleep.)
21:45:57  * brianloveswordsjoined
22:02:43  * dmuellerpart
22:13:57  * substackquit (Ping timeout: 245 seconds)
22:14:54  * substackjoined
22:21:41  * kevinswiberjoined
22:23:03  * kevinswiberquit (Remote host closed the connection)
22:25:33  * brianloveswordsquit (Quit: Computer has gone to sleep.)
22:28:00  * brianloveswordsjoined
22:58:37  * mcollinaquit (Remote host closed the connection)
22:59:10  * mcollinajoined
23:01:52  * jjmalinaquit (Ping timeout: 240 seconds)
23:03:34  * mcollinaquit (Ping timeout: 264 seconds)
23:14:20  * fritzyquit (Ping timeout: 244 seconds)
23:15:16  * fritzyjoined
23:19:41  * jerrysvquit (Remote host closed the connection)
23:59:45  * mcollinajoined