Hi I'm also quite interested in this library as I have this enterprise application, which uses XML quite heavily. The XML DOM is as it currently stands is being serialized to a XML String for moving between processes. As Xerces-C and Pathan (XPath) allows one to provide your own memory manager, it will reduce XML DOM generation to happen only once for it's lifetime instead of once in each process it visits. I don't know if this is at all possible, especially considering the problems with the vtables, but hey it will be fun to find out :) An initial comment is that a suggestion to make a shared-memory policy that defined how to create the region. Some of the possibilities could be * Bound/fixed memory address - for OS's that support that - like Windows and Linux * Unbound memory address The fixed memory address would not need offset_ptr and if start memory address is fixed, the vtable problem might actually not be an issue for that creation policy. /Anders Ion Gaztañaga wrote:
Hello to all,
As promised two weeks ago, I have a first rough version of shared memory library in Yahoo Files. I've renamed and reenginered the classes from my STL in shared memory article and boostified almost all parts. The file is in:
http://groups.yahoo.com/group/boost/files/boost.shmem.zip [snip]