TJ
TJ
hmm I keep coming across more and more use-cases for this. Even if I pushed them to another nsqd or topic I need to process those per-client as well, and...
yea I was thinking about FIN/PUB, I guess the downsides I can think of would be: - it's not atomic - publishing would introduce another localized NSQD (unless we could...
no worries! It's nothing too urgent on our end
yup! we could definitely do that instead
nope just individual nsqd granularity
I saw some pooling thing in the source but I didn't look at that part too close not sure what that's for, but in general if you have N concurrent...
plus there's also the adoption problem in node since everyone uses callbacks
@jasonkuhrt you wont have any problems at all in cases like that. I think the biggest problem facing node as far as coroutines go is a) start with small growable...
ah I see, the `.wait()` stuff. That's definitely better than callbacks, but ideally if a community was built ground-up with coros as "the" concurrency model we'd just have nice `fs.read(file)...
lame :( I see this as well