Domains Planning

[mikeal]

I'd like to use this ticket for planning the domains session.

I expect this session to have slightly more "talking" than a normal talk but I don't want that to take up so much time that people don't work with some real code.

I think a "sample app" is a good idea, something that is very simple but has more than one point where you can make it fail and it won't be trapped properly and people can add in support for domains and figure out, on their own, the best places for them.

I'd like to stay away from requiring any extra services or non-standard APIs. The redis client is a great use case but we don't want to run at the camp, or have each person run, a redis server. And I'd also like to stay away from any flow control libraries only because no more than 50% of the attendees will already be familiar with which ever one you choose.

@othiym23 @domenic

[othiym23]

@mikeal, if you can, wait for @domenic's sign-off that he's ready, but I have all of my source in. If it's messed up, I guess we'll just make that part of the exercise.

@domenic, I reworked the Express example a bunch, and tested that the domainifier I sketched out above actually works as expected (it does). Let me know if there's anything else specific to Express you'd like me to incorporate in the slides.

[othiym23]

The proof of work server example crashed so frequently and so messily that cleaning up after it was a pain in the ass. I made crash more hygienically, and also make the connections in the pool do some work at startup so the pooling is more justified. I'll leave it alone now.

[domenic]

Everything looks great to me. I like the express example with both possibilities.

[othiym23]

Slides are added under slides/domains. Lots of code and probably too many complete sentences. Let me know where I should expand and if there's anything I should remove.