[AFS3-std] XCB union decoding (was Re: Encoding IPvN addresses)

[Matt W. Benjamin]

Hi,
----- "Andrew Deason" <adeason@sinenomine.net> wrote:

> But in that situation with XCB, if you get an unknown callback type,
> there's not anything you can do with it, so the only thing I can see
> happening is that you drop it. And so, you've dropped a callback
> break,
> which means losing information or keeping stale data around in the
> cache. 

Maybe, yes.  The potential impact of dropping an XCB depends on the message (esp. as it evolves).  All but one of the original XCBs are effectively breaks.  The current flock XCB interface is a bit different, etc.

>I would expect that the fileserver be told that a client
> doesn't
> understand a certain callback type, and so would have to work around
> it
> (probably by sending a Cancelled or something).

Yes, there is a need that type of information, possibly at both ends.

> 
> -- 
> Andrew Deason
> adeason@sinenomine.net
> 
> _______________________________________________
> AFS3-standardization mailing list
> AFS3-standardization@openafs.org
> http://lists.openafs.org/mailman/listinfo/afs3-standardization

-- 

Matt Benjamin

The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel. 734-761-4689
fax. 734-769-8938
cel. 734-216-5309