[972] in Coldmud discussion meeting

root meeting help first first in chain previous in chain previous next next in chain last in chain last

Re: [COLD] 'user()' builtin function..

daemon@ATHENA.MIT.EDU (Tue Apr 23 11:00:57 1996 )

Date: Tue, 23 Apr 1996 09:38:56 -0500 (CDT)
From: Stephen Smoogen <smooge@duracef.shout.net>
To: Brandon Gillespie <brandon@tombstone.sunrem.com>
cc: coldstuff@cold.org
In-Reply-To: <Pine.BSF.3.91.960422125842.3006A-100000@tombstone.sunrem.com>

On Mon, 22 Apr 1996, Brandon Gillespie wrote:

> Ok, I'm breaking down here.  Should we add a 'user()' builtin?  This 
> function would go alongside 'sender()' and 'caller()', it would be more 
> appropriately called 'controller()'.  Since ColdC is developed for a 
> multi-connection server environment it only makes sense that there would 
> be a central object to control a single 'connection'.  How this builtin 
> would work is there would be a controller variable which defaults to the 
> connection starting the task, but allow the task to set a different 
> controller as things go..
> -Brandon Gillespie-
> Do you prefer 'user()' or 'controller()'?

I would go with either controller() or requestor()... but prefer 
controller(). The reason being is that I could have an AINPC running 
around in the enviroment or some other item. It would not be a user 
though... (just semantics).


Stephen John Smoogen 	
Recovering Sysadmin (well ok... I still sysadmin... I cant stop)..