Ohhh.... Be careful, Ann; I'm about to get greedy :-)

Things that might make my life simpler:
. the IP address from the connection (returns blank if the user did not
connect using TCP/IP)
. a server timestamp with the moment the connection was established (useful
to find out about connection uptime, usage, monitoring activity, etc...)

What about "blr_user_info" instead of "blr_user_id" ? - after all, eg, the
user's transaction is not his identification.

Marcelo Lopez Ruiz

----- Original Message -----
From: "Ann W. Harrison" <aharrison@...>


> So, what would the world think of reserving 174 to
> be blr_user_id. That would take a single blr argument
> which would be one of the set
>
> blr_user_transaction
> blr_user_connection
> blr_user_role
> ...
>
> where ... would expand as necessary.
>
> Thoughts?