bf_connect_player()

• Date: Tue, 6 Aug 1996 09:04:57 PDT
• From:
  Colin McCormick <colin@tripod.tripod.com>
• Content-Type: TEXT/PLAIN; charset=US-ASCII
• Fake-Sender: MOO-Cows-Errors@parc.xerox.com
• In-Reply-To: <v03007800ae2b60403109@[132.76.55.130]>

On Mon, 5 Aug 1996, Gustavo Glusman wrote:

>  --> ANY :do_login_command call that returns a valid object number <--
>  --> that is_player(), will result in a connection (assuming the   <--
>  --> resources are available etc).                                 <--

Thank you, Gustavo, though I do in fact understand this point, and the
point of the in-db line buffering code people posted earlier.  I simply
think it would be cleaner and more efficient not to have to call
:do_login_command() multiple times and buffer lines in-db.  Hence, I'd 
like bf_connect_player().

> Actually, there's no need to store the USER info in the database, nor on
> temporary variables of some waiting task. Let me leave that as an exercise
> to the reader. :)

[monitor] (Request from connection #-140.)
;add_property(#-140, "something", 1, {#2, "r"})
=> #-1:Input to EVAL, line 1:  Invalid argument
	...

Hmmm ... well, too clever for me!  :)

Colin
Tripod, Inc.
http://www.tripod.com

• Re: bf_connect_player()
• From: Gustavo Glusman <bmgustav@bioinformatics.weizmann.ac.il>

• Re: bf_connect_player(CONN, PLAYER) --> *FTP!!*
• From: Gustavo Glusman <bmgustav@bioinformatics.weizmann.ac.il>

• Prev: BF proposal: bf_superuser()
• Next: Re: bf_connect_player()
• Index: MOO-cows
• Thread: MOO-cows