G33X Nexus Entertainment
G33X Nexus Entertainment => Current Projects => RaptorNL => Topic started by: contingencyplan on September 18, 2006, 12:59:14 pm
-
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.
-
Actually, I think that we should either replace Hawkthreads, or simply keep them. Threading is one of the (rather large) speed enhancments done in HawkNL...
-
Okay. I haven't looked at it yet, but I figured I'd get what feedback I could so I have in mind how I'm going to proceed on that one. In this case, however, I may replace it with the Boost library's version. One main thing to keep in mind is I am developing a networking library in and of itself; I'm not trying to tie it in with CS directly.
-
Correct.Interoperability with CS is not a concern, nor should it be. I would use boost, or keep what's there (as I believe it's wrappers around native libraries).
-
I would use boost, or keep what's there (as I believe it's wrappers around native libraries).
That's my understanding as well. I don't know the difference between what's there and boost's. The reason I'd lean towards Boost's, however, is to use something that's already there and tested a LOT. The Boost libraries are well known, well-tested, known to be reliable, and (most importantly) remove one more thing I have to code up myself and keep track of.
-
I'd lean toward using as much Boost as possible in RaptorNL for exactly that region... they're well-tested, cross-platform C++ libraries that are freely available, and that's less code we need to maintain. ;)