I've noticed in the HawkNL source code there's the HawkThreads headers and source code. Currently, I'm thinking that unless there's a requirement for it within the networking portion of the library (i.e., the threading is inextricably entangled with the networking), I'm just going to take that library out completely. There's other multi-platform threading solutions (CS has theirs; if I was starting a project from scratch, I'd probably use Boost's), so I don't see the need to complicate the networking library by trying to also work with the threading library.
Any thoughts? If somebody wants to take over the threading library, they're more than welcome to. I may want to take it back later, depending on what all happens, but for now I don't see a need for it.