On Thu Feb 2 11:57:10 CST 2006, [EMAIL PROTECTED] wrote: > yes, i supposed it could be something along those lines but i didn't make my > point clear. > if it is along those lines, it breaks something that even sockets didn't > break. > at the moment, i get a file descriptor that i can pass to anything that does > read and write.
definately not true on linux. udp and netlink sockets would be a counter example. > now i've got something that i can only mmap, and even the mmap refers to a > non-trivial data structure shared with the kernel, and the recipient of the > file descriptor > must invoke special calls in a special library (ie, the `access method'). > i suppose you could call it TCAM > i think you're confusing "moving" bytes around with using said bytes with a context. any file that you read or write can be viewed as either a series of bytes or a complicated data structure. either mmap or read/write will let you do that. take /etc/passwd on linux. you can read(2) it or you can use setpwent/getpwent/endpwent if you'd like to view it as a data structure. - erik
