World: r3wp

doesn't fix the long lags, though

in fact, you can drop this line completely, i think

because a WRITE on the tcp port from within the tcp port's awake 
handler automatically re-schedules the tcp port for event handling

ok, working with line removed ..  but still delays

mhm

only chasing thru your code, atm :)

ok, the flow should be, imho:
- read WAITs on the cmdport

- if the cmdport needs to open a dataport, cmdport WAITS on dataport

port/state/connection is your cmdport, if i'm not mistaken

so i started by changing the read actor to:
		read: func [port [port!]] [
			wait port/state/connection
		]
which should break things hard :)

and yes it does, hangs after SYST

next step: tracing if your awake handler returns true in this case

wuah, huge switch :)

but, as expected, it does not :)

client/spec/ready seems to be a good flag to use as return value 
for the awake handler

unfortunatly, in the AUTH 230 handler, you set both ready to true 
_and_ issue another write

assuming that the SYST is rather worthless anyway, i drop the write

ready is set to true so I can process the SYST

i'll abuse ready is the return value from the awake handler, for 
now :)

I did this as otherwise I ended up pipelining the ftp server :(

don't they like that :) ?

not if they don't support pipelining!

:)

btw graham, do you happen to have heard of git?

repository thingy?

yep

used it, by any chance?

yes :)

nope ...

wow, fixed it :)

Umm... does Ubuntu use git ??

i use git

I know I installed something which failed to work for me ... in downloading 
from the ubuntu repository

and if you'd be using it too, developing protos together would be 
much more fun :)

so what's the fix?

dropped the SYST write from 230

I think that might help with directory parsing ...

made the last "read client" in the read event handler block conditional:
unless client/spec/ready [read client]

in case it's an Amiga ftp server ...

:)

returned "client/spec/ready" instead of "false" from the awake

one problem remains: the read after RETR does not return

hmm... my 0.0.5 added a return true

on a successful download

so just comment out line 261 ?

write-cmdport/only client [SYST]

so where do I set the state then?

here's a diff of my changes: http://gist.github.com/274796

that's a diff against the 0.0.5 from wik.is

wow .. you managed to nuke my 'read !

hehe :)