[OpenAFS-devel] [Fwd: Request for a capability bit for RxOSD]

[Felix Frank]

This is a multi-part message in MIME format.
--------------070206060304030808030106
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi all,

this has been pending approval for the afs3-standardization list since 
Monday. That seems not to have ever been of any consequence so far (none 
of my messages ever made it onto the list). I admit I'm somewhat annoyed 
by that. Anyway - would one of the members relay?

Of course, comments from everyone on here are appreciated as well (on 
the request that is, not the submitting procedure).

Thanks in advance.
Cheers
  - Felix

--------------070206060304030808030106
Content-Type: message/rfc822;
 name="Request for a capability bit for RxOSD.eml"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="Request for a capability bit for RxOSD.eml"

Message-ID: <4A365A0D.2060603@Desy.de>
Date: Mon, 15 Jun 2009 16:26:21 +0200
From: Felix Frank <Felix.Frank@Desy.de>
User-Agent: Thunderbird 2.0.0.21 (X11/20090324)
MIME-Version: 1.0
To: afs3-standardization@openafs.org
CC: Christof Hanke <christof.hanke@rzg.mpg.de>, 
 Hartmut Reuter <reuter@rzg.mpg.de>
Subject: Request for a capability bit for RxOSD
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

For OpenAFS+OSD, it would be helpful for the clients to identify OSD 
capable fileservers early. Codepaths can then be separated more easily 
for OSD access vs. normal fileserver access.

Similarly, fileservers can store a hint about clients that are OSD 
capable, and send OSD-related data only to those. Other clients will (as 
is the case already) be forwarded actual file data instead of being 
supplied with OSD metadata.


--------------070206060304030808030106--