 |
 |
Hi Andy, > >> The redir opaque data will be added to the filename with a "?" in >>front of it. The redir opaque data will not be forgiven by the client, >>so every future open will have it, unless it is overwritten by another >>kxr_redirect. > > That's an interesting statement. I assume you mean that the token will be > passed on future opens to the same server for the same file (i.e., when > doing a recovery reconnect). Opens directed to the redirector for new > files or even the same file should not pass opaque token supplied by the > redirector (not that it would hurt). Well, I do not understand completely. Here is the actual behavior: - We have two strings that can be passed by a kxr_redirect: - a "login" token which will be passed to the dest server in the login phase and then cleared - an "open" opaque info which will be passed to the dest server in the open phase. This is not cleared, but can be overwritten by a subsequent kxr_redirect. This is the way I interpreted the proto specs. How does it sound to you? > > Now, the redirector does not supply an opaque token the will that be taken > as "no token" to pass? > Argh, I do not understand... Please translate! Fabrizio > Andy