I know how they work.
I said you need a filesystem to read data.
You then said no, and that RAW can be accessed like a filesystem under unix.
I then said RAW is a filesystem since it can be read and written to, and the terminology used to describe it by others treats it as a filesystem.Your definition of filesystem is wholly incorrect, then. It's like calling
anything you can put a penis into a "woman". Yes, you can write to a filesystem (and put your penis in a woman), but it doesn't mean that all reading/writing is done with a filesystem.
The concept of "sockets" is one such alternative where you can read and write in a network without a filesystem being involved.
http://en.wikipedia.org/wiki/Internet_socket
http://help.adobe.com/en_US/FlashPlatform/...net/Socket.html
A more broad example off the internet would be piping data streams between processes.
http://en.wikipedia.org/wiki/Pipeline_(Unix)
Again the Unix standard is a reference because unlike most ordinary things with Windows, with Unix and it's tools you're often exposed to the stuff below that you normally deal with.
Nollog said:
Netscape is the basis of firefox iirc.
Cache being on or not isn't the issue.You said that it HAS to be written to the filesystem. This is false as it's possible to load and display pages without writing them to the filesystem first (or at all).
QUOTE(Nollog @ Mar 1 2011, 05:05 PM)
All I said was that data needs to be read and written from a filesystem by the browser.
You referenced the OSI model.