Contexts about kit HOT 6 CLOSED

http://godoc.org/github.com/spacemonkeygo/monitor/trace is one possible example of the way this benefits things.

Internally at Space Monkey we also have a disk operation library that distinguishes disk operations as being background (cron-type jobs or something) or foreground operations (user-requested) using the existing context, to determine what priority in our application-level disk queue the operation should go (in an attempt to keep low-level queues shallow)

from kit.

Yes, package server will need to make sure contextual information isn't lost in translation between services, and I definitely hope to leverage package context for that. Hopefully it's possible to implement without modifying server interface definitions, i.e. by mandatory chaining of a Contextual (or similar) handler. All to be determined.

If you're interested in package server, maybe you'd like to join Freenode #gokit and find some other interested parties to take ownership of the initial package server RFC?

from kit.

@peterbourgon: Would it make sense to create Github issues for each of the RFCs, where structured, scoped pre-proposal discussion can take place? I think focus is paramount given the spectrum of problems to be solved here.

from kit.

@tsenart yes, I think that's a logical next step.

from kit.

@tsenaet +1 to that idea.

from kit.

This will be addressed in the first-draft implementation.

from kit.