Hi Hartmut, Felix, I see the point, it's not useful if it's only for decoration. It does feel intuitively right to have txid, if it could be used by a family of RPCs. Might make for cleaner interfaces for cancellation, abandonment, (not to mention futures--reversibility, delegation, ...)?
Matt ----- "Hartmut Reuter" <[email protected]> wrote: > Matt W. Benjamin wrote: > > Hi Hartmut, > > > > Does using GetODSDlocation and StoreMini as begin/end I/O RPCs > allow > > use of an opaque identifier to refer to an I/O transaction? > > > > Matt > > > > As Felix already said: allowing only one write at a time makes it > unnecessary to have an identifier for the transaction. For the error > log, however, I would keep the IP-address in the structure so that in > case of problems you later can find out what happened. > > Hartmut > ----------------------------------------------------------------- > Hartmut Reuter e-mail [email protected] > phone +49-89-3299-1328 > fax +49-89-3299-1301 > RZG (Rechenzentrum Garching) web http://www.rzg.mpg.de/~hwr > Computing Center of the Max-Planck-Gesellschaft (MPG) and the > Institut fuer Plasmaphysik (IPP) > ----------------------------------------------------------------- > _______________________________________________ > OpenAFS-devel mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-devel -- 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-devel mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-devel
