site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com On Jan 22, 2006, at 12:02 PM, darwin-dev-request@lists.apple.com wrote: I want to be able to capture the I/O calls of an application and then ship them back over the network to be handled by another machine. = Mike _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... There are plenty of examples of this in the system already; they're called "network filesystems". One of them is even called "the Network File System". It also seems like Apple could keep the system call interface stable between versions - the great thing about system calls is if you need to change the meaning of one, you can just create another system call with a different name. You can leave the old one stable, and just change the framework to call the new one - if someone has found a way to call the actual system call, the can keep using it. This is a naive assumption. It is much easier to version at the shared library interface; locking down the system call layer introduces a lot of problems, especially if you guarantee the interface as ABI. This email sent to site_archiver@lists.apple.com