4 Nov
2009
4 Nov
'09
2:39 p.m.
jmpulido escribió:
It seems that the shared memory is actually managed by means of a file in disk that probably the user is creating in a location and the service in a different one.
This should be fixed for Boost 1.40, which version are you using?
which has not been very helpful since I have no clue on how to use boost::interprocess::managed_windows_shared_memory or even if it could serve to my purpose somehow.
managed_windows_shared_memory is similar to managed_shared_memory but the memory disappears when the last attached process ends and uses native windows shared memory instead of file-based emulation. Best, Ion