Matt Reiferson

@Dieterbe trying to land `1.0` first (this would _definitely_ not be in that release and would likely be a "2.0" kind of thing)

I rebased this god forsaken branch yesterday and also wanted to drop this in here as a likely superior data structure for managing FINs/offsets: http://web.engr.oregonstate.edu/~erwig/papers/Diet_JFP98.pdf

@nvcnvn might make sense to make that public, we've taken this position to avoid issues of compatibility guarantees, but this package could be generally useful. What do you think @jehiah...

@lootch thanks for looking into this! If you're up for it, open any PRs that address the issues you find.

Wow, thanks, this is great! In a similar vein to @ploxiln's comments, I would love to start by reading some design and architecture docs to better understand _how_ you've accomplished...

> Yeah, I think the first thing need to be done is: every message should be written to the disk file without involving the channel overflow to disk. All theses...

> Dynamic Log level and more detail logs This is now happening in #892. Please review if you haven't already. > After reviewed the changes, I noticed that WAL is...

@absolute8511 taking a step back, how do you propose we begin the process of discussing design and architecture? Assuming we reach consensus on those things, we can then discuss implementation...

Sorry I'm late following up on this — I feel like we should investigate how we could structure this using https://golang.org/pkg/plugin/. It would be linux-only, but it would allow us...

Hah! I guess my position is that, unless it's truly going to be an opt-in plugin model, then why jump through all the hoops with internal code to structure it...