Re: bf_connect_player(CONN, PLAYER) --> *FTP!!*

• Date: Thu, 1 Aug 1996 23:09:14 PDT
• From:
  Ahn Jin-su <jsahn@ee.snu.ac.kr>
• Content-Transfer-Encoding: 8bit
• Content-Type: text/plain; charset=euc-kr

> and then read the next "pass YYYY" line *before* deciding on whether or
> not to log in the connection.  This is not currently possible (except with
> non-blocking I/O in a polling loop, very laggy as previously discussed)
> but would be with a "connect_player()" builtin.  The :do_login_command()
> on the listening FTP daemon object would simply do what blocking read()s
> it needed and decide whether to call "connect_player()" or print a "530
> Login incorrect" message. 
> 

Another way to see it; I wrote a patch for blocking read() in 
:do_login_command() almost a year ago.

	-- Ahn

-----
Ahn, Jin-su    				email:	jsahn@ee.snu.ac.kr
School of Electrical Engineering	LambdaMOO: Deedlit(#103811)
Seoul National University, Korea

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

• Prev: Re: bf_connect_player(CONN, PLAYER) --> *FTP!!*
• Next: Re: bf_connect_player(CONN, PLAYER) --> *FTP!!*
• Index: MOO-cows
• Thread: MOO-cows