Whomever used this term, doesn't understand how a computer works (let me
guess you found it in Microsoft's documentation - would not surprise me) --
everything is a memory resource.
Accessing a file for example, the file could reside in RAM memory (aka the
cached by OS), it could reside in the cache on the hard drive. Since most
hard drives support DMA the CPU doesn't get involved that much in the
transfer of data from one resource to another. But lets be clear, every
resource on your PC uses a memory address, if it didn't, it could never be
accessed.
I think what the term is really referring to is loading the contents of a
file into a variable/structure -- depending on your buffer and structures
you'll consume RAM accordingly. Your code can determine how much memory you
use during the process of reading the file, what you elect to save, dump,
buffer sizes, etc. etc. The better applications will scale the file IO &
memory usage operations based on physical hardware (such as how much RAM is
installed and available on the PC). The less optimal applications will let
the OS decide and cache away.
Rob.
"cashdeskmac" <ca*********@discussions.microsoft.comwrote in message
news:A0**********************************@microsof t.com...
Hi,
can anyone explain the difference between a memory resource and a
non-memory
resource. I have been shown an example of error handling for a non-memory
resource (accessing a file) but am not sure what the terms refer to.
A few examples of each would be ideal.
Many thanks.
