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

[Matt W. Benjamin]

Hi,

The 'experimental' XCB now has a per-entry result by default, I need to issue a new draft with this and related changes.

Matt

----- "Jeffrey Hutzelman" <jhutz@cmu.edu> wrote:

> --On Friday, February 11, 2011 11:12:58 AM -0600 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. 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).
> 
> I think extensible unions are a good fit for XCB, because of the bulk
> 
> delivery mechanism.  But yes, you'd need a way for the client to
> indicate 
> to the fileserver which of the XCB entries it understood, and perhaps
> to 
> return a per-entry error code, in the same way that RXAFS_BulkStatus
> does.
> 
> -- Jeff
> _______________________________________________
> 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