Hi,
>Seems I have sometimes used Userreference and sometimes userreferance
>argument in my growing application.
>
>I would think it is important to be consistent and use one or the other but
>not both.
>
>I had at least one incident where clicking on a links where they were
>different ended up bring up someone else's information.
>
>So which is best to use or are their times when one is needed instead of the
>other?
>
>Should I change them all to one or the other?
>
>Why do we have both?
Convenience.
For some user at your site, <@USERREFERENCE> would evaluate to something like:
1234567890abcdefgh
That is, just the user reference ID, aka, "session key".
<@USERREFERENCEARGUMENT> will evaluate to something like:
_UserRef=1234567890abcdefgh
That is, the User Reference value, plus the argument name '_UserRef' plus
the equal sign, conveniently prepended to the value.
<@USERREFERENCEARGUMENT> is merely a convenience so I can type:
<A HREF="some.taf?<@USERREFERENCEARGUMENT>">blah</A>
Instead of:
<A HREF="some.taf?_userref=<@USERREFERENCE>">blah</A>
which is prone to my mis-typing.
So, if you are adding them to links or form actions, use
<@USERREFERENCEARGUMENT>.
If you want just the user's session ID (for example you are adding the
user's reference argument to a database table), then use <@USERREFERENCE>.
BTW, you can easily create a simple TAF with just one results action, type
in the tags, run them from your browser, then check the results. That's a
good way to find out what a meta tag does or outputs.
Eric
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
