in reply to Perl forking and shared memory strangeness under Windows
The whole fact that "fork doesn't really fork" should be enough to scare people away from doing it...of course, naming the method fork() doesn't seem to advertise that fact very well.
Since this app is pure Win32 (using the Win32 memory mapped file stuff), it makes sense to remove the forking altogether...after all, forking on Win32 is pretty much a hack...could it be moved over a threaded model, with locks (if needed) where needed?
|
|---|