[OpenAFS-devel] Re: on sockets and devices in AFS

[Chas Williams (CONTRACTOR)]

In message <4C93A15E.4070708@secure-endpoints.com>,Jeffrey Altman writes:
>In the meantime, no client today is capable of using these future object
>types and as a result I believe that the proper behavior for today's
>clients is to maintain the object locally and mask it from the file
>server.  That way it becomes possible for future local pipes to be
>created within the file system directory without breaking today's
>clients that will not know what to do with them.

like i said before i am not sure this is a good idea.  for instance,
google chrome creates a named socket in your home directory in
.config/google-chrome.   if you run chrome again on another machine so
google chrome might think that no one else is using that .config directory
since named sockets are only maintained locally.  but the other files in
.config/google-chrome would appear to be global.  this is inconsistent
and possibly confusing to an application.  of course, if we expose the
named socket as just a file for older clients (without any obfustication)
google-chrome probably just try to remove the file so it can create its
named socket.