expose event base from IOThreadPoolExecutor
authorJames Sedgwick <jsedgwick@fb.com>
Wed, 1 Oct 2014 17:32:54 +0000 (10:32 -0700)
committerAndrii Grynenko <andrii@fb.com>
Wed, 15 Oct 2014 00:46:53 +0000 (17:46 -0700)
commitca5fc3666621fbfe0ce1211e32ebe5f646e9af0c
treeb92a6a1e12b7523c8dc9cb4285dbbdbb969355de
parent5617e556f7b806027b0105996a8f1f45ea294d49
expose event base from IOThreadPoolExecutor

Summary:
I'm not 100% sure this is the best way to go about this but I don't hate it either.
I'm going to start seeing how it might fit into tserver - my guess is that some sort Cpp2WorkerFactory which also manages those objects would get plugged in as the thread factory
Haven't fleshed out how this would relate to TEventBaseManager

Test Plan: added unit, starting to play with this in Thrift2 server

Reviewed By: davejwatson@fb.com

Subscribers: alandau, bmatheny, trunkagent, fugalh, njormrod

FB internal diff: D1574660
folly/experimental/wangle/concurrent/CPUThreadPoolExecutor.cpp
folly/experimental/wangle/concurrent/IOThreadPoolExecutor.cpp
folly/experimental/wangle/concurrent/IOThreadPoolExecutor.h
folly/experimental/wangle/concurrent/ThreadPoolExecutor.cpp
folly/experimental/wangle/concurrent/ThreadPoolExecutor.h