Memory-mapped files - pros and cons of mapping view on whole file 
Author Message
 Memory-mapped files - pros and cons of mapping view on whole file

anyone know of the pros and cons of setting up MapViewOfFile to  view
the whole of a memory mapped file? This seems to be the easiest /
recommended? option in the MemoryMappedFile class. It certainly seems
straightforward to map and view files up to 100MB in this way (I was
limited by disk space for bigger files), but what is the "cost" of
setting the view on the whole file, compared with setting smaller views
and unmapping and remapping as required? The latter requires handling
the views of course.
Any ideas,

Sun, 29 Aug 1999 03:00:00 GMT  
 [ 1 post ] 

 Relevant Pages 

1. memory mapped files for index-files

2. Memory Mapped files: Volume for a file externally altered

3. memory mapped files for index-files

4. IPC: Shared memory via dll vs memory map file

5. copying CObject-derived-classes to shared memory (created using Memory-Mapped file)

6. Application config files - pros and cons

7. problem appending data to Memory mapped File in Unix

8. ANSI C way to memory map a file?

9. Memory Mapped File Example, Please?

10. Updating memory mapped file

11. Memory mapped file question

12. Growable Memory Map-File


Powered by phpBB® Forum Software