You can subscribe to this list here.
| 1999 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2000 |
Jan
(5) |
Feb
(5) |
Mar
(4) |
Apr
(3) |
May
(13) |
Jun
(8) |
Jul
|
Aug
|
Sep
|
Oct
(4) |
Nov
(3) |
Dec
(5) |
| 2001 |
Jan
(10) |
Feb
(6) |
Mar
(38) |
Apr
(27) |
May
(28) |
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
(2) |
Nov
(2) |
Dec
(4) |
| 2002 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Eduardo J. B. <ej...@ne...> - 1999-12-21 22:24:07
|
davids wrote: > > I'm porting nb++ to solaris 2.6 Great! > and looking at using a boss-worker > threading model. I looked at the samples and while the serversocktest > example does what I need, I'd rather use a threadpool as in > threadtest-multi. The threadtest-multi does a many to many thread > model which won't work for what I need as I have a function which > is called as a registered event. > I did notice MultiThreader, which returns a ThreadPool object, > in the documentation. And I see an example of that in the daemontest, > so it looks like I could use NetworkDaemon as my example and derive > from Daemon to do what I wish. So, am I on the right track? NetworkDaemon allows several 'threading models' to be pluged into it. In particular, MultiThreader() (daemontest -p) implements a Boss/Worker model with a pool of threads, similar to Apache's processes to avoid the creation overhead. The main thread acts as the boss, while the threads on the pool are the workers. If your program takes things from the net, NetworkDaemon is a good choice. Else, it's a good starting point, IMHO. You could use the same threading strategies (they should be fairly generic, I'm open to changes), but with different input source. > It may take a couple of weeks and the result could > be ugly (#ifdef SOLARIS) but when I get it running I'll get the > code back to you, (better I should use CVS?). It seems the linker > that comes with Solaris 2.6 is giving me problems, so I'll > try the GNU one. I'll keep you updated. I understand your problem, I've gone thru a lot of headaches to try to minimize OS dependant stuff to osdep.hpp for the HP/UX port. Once it's working we'll see how we can make it. neater. Ej. |
|
From: davids <da...@da...> - 1999-12-21 18:23:35
|
I'm porting nb++ to solaris 2.6 and looking at using a boss-worker threading model. I looked at the samples and while the serversocktest example does what I need, I'd rather use a threadpool as in threadtest-multi. The threadtest-multi does a many to many thread model which won't work for what I need as I have a function which is called as a registered event. I did notice MultiThreader, which returns a ThreadPool object, in the documentation. And I see an example of that in the daemontest, so it looks like I could use NetworkDaemon as my example and derive from Daemon to do what I wish. So, am I on the right track? It may take a couple of weeks and the result could be ugly (#ifdef SOLARIS) but when I get it running I'll get the code back to you, (better I should use CVS?). It seems the linker that comes with Solaris 2.6 is giving me problems, so I'll try the GNU one. I'll keep you updated. -Dave Sheckler |