World: r3wp

btw, here's the source link to the pop3 seq diagram: http://bit.ly/4q0ADG

One good thing .. on r2 I doubt I could download a 500Mb file using 
ftp .. but I'm nearly there now and the windows task manager is only 
showing 12Mb of ram usage with 0-1 % cpu

very nice

We need some standard network error handlers too .. like if the password 
is wrong etc.

the other, more traditional approach, would be something around copy/part

(for your data streaming question)

except the r2 ftp scheme doesn't support that ... AFAIK

ftp: open ftp://...
write/append %... copy/part ftp 10240

don't care about R2 :)

(I don't)

wrap a `while [not tail? ftp] [....]` around this

My issue with the schemes is that the interface to them was always 
too restricted ...

yeah. don't know if that's even possible in R3 at the moment

so we had to hack the schemes to add eg. 'TOP in r2 prot-pop

i think a COPY actor will be there, but i guess tail? won't

so instead of directly interacting with the scheme, we need an intermediate 
level ...

tough issues

what would you like the error handler to do in case the password 
is wrong?

just raise some standardised error!?

yeah ...

I just use Gabriele's http-error ...

but these things should be defined in a common network kit

most definitely, yes

a module

net-tools

or even netkit :)

if R3 modules wouldn't suck so hard :)

640mb iso image downloaded successfuly!

nice

md5sums match :) ?

7zip opens it up ..

great

Uploaded my latest version which by default downloads ubi.exe which 
is a 1.5mb file ( ubuntu windows installer. )
You can uncomment the 650 mb download if you want to try :)

we really ned to get rid of those WAITs :)

I haven't done it yet, but if one gets an error code, it should probably 
throw an error.

or maybe the server is so slow :)

the debian server was really slow ... I had to wait 7 seconds for 
it to respond

i guess i'll try a local ubuntu mirror

but using a timeout for some reason means that it defaults to the 
timeout value ?

so every command uses the timeout .. so don't understand that

you wait [port timeout] ?

yes

strange

well try it and you may see it ...

i have a huge wait after SYST

ah, i guess i should try with the win32 r3 instead

ok, still. long wait after SYST

then after 227 PASV

yes ... shouldn't happen

ah, i think the culprit is that you WAIT inside the awake handler