632 karma · joined March 16, 2009
--> http://mhausenblas.info
*) https://help.github.com/articles/archiving-a-github-reposito...
Joking aside: since I've used Kafka for the reference implementation it naturally looks very similar, yes but it's really about the semantics. For example, does your 'normal' Kafka consumer start from the beginning or use latest index, etc.
No. Each message is delivered at most once. But good point, need to make that clearer!
> Do messages ever get removed from dnpipes without a reset.
No. Again, something I need to clarify as it seems.
> Does pull block, support async completions, or just return an error when no data is available?
It blocks.
> Reset, rather than sending an EOF which passes through the queue, implies that shutdown is either drastic or requires external coordination to empty the queue and stop the sending end before the reset.
I don't follow. Reset empties the underlying queue.
In general, since the consumers start to consume not from the beginning of time (as in Kafka's `--from-beginning`) but wherever they happen to be (that is, in Kafka terminology from `latest` index) this shouldn't be a problem.
I tried to model as close as possible and as it makes sense after the semantics of (local) named pipes. I might have fudged up here but I'm not 100% clear on where :)
I'm all open for GitHub issues that capture this request and/or PR ;)
[1] https://dcos.io/ [2] https://medium.com/none-size-fits-it-all/u-cant-touch-this-9...
https://medium.com/@mhausenblas/serverless-get-in-the-sea-49...
Cheers, Michael
Cheers, Michael
Cheers, Michael
PS: To be honest, I was also sort of surprised to see him calling the audience like 'speak after me'. However, I was positively surprised - I really like when people put enthusiasm in things and not only give interesting but boring talks. In that sense I very much support TimBL to continue this (though, maybe not go as far as Steven B. at MS did with his infamous 'monkey dance' ;)