I don't really understand this question. What's a function or file to do if I ping them, talk to them with TCP/HTTP, or otherwise communicate? I suppose I coul

I don't really understand this question. What's a function or file to do if I ping them, talk to them with TCP/HTTP, or otherwise communicate? I suppose I could imagine a system like that. Files could be IPv6 addressable entities that can communicate using some file access protocol, and functions could be entities that receive their arguments as the IPv6 packets I send them and that could respond with whatever their return value is. This is too different from current OS conventions, though. Also, I'm not sure what the benefits would be. If I have an IPv6 address, how would I know that it's a local file and not a host on the other side of the planet? Wouldn't that be a problem? If a directory tells me it has a file with a certain IPv6 address, and I try to open it, is there the possibility it would send a file open request to a host elsewhere on the planet? Would I be waiting for a response to open the file until the host replies that it doesn't serve that protocol?