Hi Tom, I recall mentioning in Ohio, XCB doesn't have a private view of client callback state. I'm unsure it's a good tradeoff to serialize XCB messages for "reliable delivery." You would be changing the goal from "consistency is preserved" to "clients don't need to update their cache" on failover--at potentially very high cost, no?
Matt ----- "Tom Keiser" <[email protected]> wrote: Secondly, > there's the question of whether extended callback data should be > serialized or not (at present, dafs+osi+xcb does not dump xcb data; > it > would not be particularly hard to add support in future). -- 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 _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
