[alicebot-archcomm] Attribute var

[Kim Sullivan]

I missed a few posts, my mailserver was down for some days, so I'm sorry if
this has been covered already.

> Yeah but you are appending the variable item to one specific user
> @ all times
> when using <set>.

Is this a problem? I mean from the AIML point of view. When I log in to an
ATM using my credit card, I have no problem that I'm affecting only my
variables.

> Those "variables" don't belong to the application, but to the
> user/session.
> A
> "variable" is something that belongs to the app itself and even then it's
> usually tied to a server property, so you either have:

This probably depends on what you mean with the 'application itself'. I tend
to view the AIML set as the application, the server is only an interpreter -
like java.exe is only an interpreter for D. The fact that I don't have to
manually key all variables to a specific user is a plus for me. I wish I
could do this in my interpreter program too, but I have to pass the user-id
and bot-id around all the time, and since I'm too lazy to do this, I'm
simply not supporting multiple users :-)

> I think when it evolves (?) and you have user lists mingling with
> other user
> lists and performing logic and comparisons and voting that's when
> the language
> takes on a mind of it's own ;-)

User data corelation? This user looks 75% like a different user, so start
asking about the as yet unknown things. "Haven't we met before?" I think
this would probably lead to some problems with protecting personal
information.

Kim