On Thursday 19 October 2006 08:02 am, Darren J Moffat wrote: > Why would you use functions from a networking library if you are only > writing to disk ?
Well, I was curious to why. I would think that appliation layers would issolate out code that was common between both architectures rather than depend on hardware. Wouldn't one be fishing for x86 hardware support after, to have common code for both platforms? But why not let ZFS handle that for you? Disks can be pulled out of one architecture, put into another, and the data is still there and accessible. ZFS will handle any conversion, and all of that is transparent to the application, AFAIK. I was confused when you spoke of meta data, opposed to application data, so wanted to understand that. The application doesn't need to worry about what architecture it's on, read/write data. This is why I was curious about the networking functions, which is what I have traditionally thought of where application data, and converting between host and network was done like that. Sounds like Sun might view things differently in that regard, or you're talking about something else, like kernel data at the application level, so ignore me...;-) If you're telling me that writing to the hardware at the application layer is what is reccomended, I didn't know that would be advocated. Seems silly to create a situation where you need to write 2 different hardware layers at the application level, that's so 70s.:-/ -- Alan DuBoff - Sun Microsystems Solaris x86 Engineering - IHV/OEM Group _______________________________________________ opensolaris-discuss mailing list [email protected]
