On 5/15/07, Alessandro Vesely <[EMAIL PROTECTED]> wrote: > Virtual memory is a feature that an OS can expose to apps. Memory mapped > files are an example. On Linux there are both shm and mmap. Traditional > SysV stuff may better suit inter-process sharing, while more recent APIs > emphasize multi-threading within the same process. On Windows there is > just one way to share memory. Memory locking must be understood in that > context. It is meant for synchronization purposes, not for security.
LocalLock() and GlobalLock() do indeed seem to be for synchronization, but VirtualLock() seems a different beast entirely. It seems its purpose is for performance and/.or security. But again, I have little experience in this area, and I am just regurgitating what I read on MSDN. -- RPM _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users
