OSS is about choices. But not all choices bring value to the community.
does it matter? the programmer's choice will carry more weight than a end user. my code always bring value to myself the only community i really cared unless it's a paid job. what community r u talking about? force something as irrelevant as config file format to ppl is not OSS's way of doing things.
what's the diff between this CSP thing and a message queue with explicit notify(win32 sendmessage)? u do understand how the system call write(...) works right?
to say the truth, there's only one true way to do the locking, all other ways r just same method in different expression.
can you IPC a file descriptor to me? threads are a lot more efficent on resource (not only memory).
BTW, if apache do used c++, it had been much better than now. a module are naturally a object, resource management will be much simpler. binary modules? you can use c if you think binary only module are better and it will run under c++.
Basically, the promise of threads is that you will not be paying the equivalent of a full process context switch overhead, because your VM and other process-specific things will not have to change when context switching from one thread in a process and another thread in a process.
not from what i see. IMHO, threads makes share things between two processing easier. how can u make a connection pool with many process? and you can do all cpu based work in a group of threads and let one thread do all other i/o based work. These things are impossible with multi process and damn hard with single process FSA.
Slashdot Mirror
does it matter? the programmer's choice will carry more weight than a end user. my code always bring value to myself the only community i really cared unless it's a paid job. what community r u talking about? force something as irrelevant as config file format to ppl is not OSS's way of doing things.
there's a reason why ppl invented those operators (in real math) and continue use it.
according to the easy to misuse theory, gun is bad. it's so easy to kill ppl using a gun.
no idea what u r saying. but power has nothing to do with voltage. u need 1000w for a sec to raise 1 lite water 1c, either it's by gas, 100v or 10v.
isnt this the direct consenquence of M$ antitrust case?
Features
Transparent Persistence for native Java business objects.
3 to 4 Orders Of Magnitude Faster than databases via JDBC.
ACIDTransactions.
Zero Bugs.
could this be a world record?
what's the diff between this CSP thing and a message queue with explicit notify(win32 sendmessage)? u do understand how the system call write(...) works right?
to say the truth, there's only one true way to do the locking, all other ways r just same method in different expression.
can you IPC a file descriptor to me? threads are a lot more efficent on resource (not only memory).
BTW, if apache do used c++, it had been much better than now. a module are naturally a object, resource management will be much simpler. binary modules? you can use c if you think binary only module are better and it will run under c++.
Basically, the promise of threads is that you will not be paying the equivalent of a full process context switch overhead, because your VM and other process-specific things will not have to change when context switching from one thread in a process and another thread in a process.
not from what i see. IMHO, threads makes share things between two processing easier. how can u make a connection pool with many process? and you can do all cpu based work in a group of threads and let one thread do all other i/o based work. These things are impossible with multi process and damn hard with single process FSA.