World: r3wp

between machines ssh (i.e. scp/sftp) and http are my main mechanisms 
of file transfer

so anything that once was ftp is now either http or ssh :)

Hylafax :)

hehe

I should start work on a hylafax scheme

oops .. need to do a STOR

again, STOR should stream a file from local storage ... and write 
a binary type

file! => stream
binary! => just write

mhm

oh yeah.. we need that  other scheme ... rpc://

hehe

i could port some xmlrpc stuff over

I'm still using xmlrpc

so do i, for some things :)

a minimal ftp login skeleton, no error handling: http://bolka.at/share/prot-ftpget.r
[temporary url]

written for readability

i think that'll be a rather typical skeleton for request/response 
protocols

Why not put false at the bottom ...

or is it the readability thing?

undecided about that

yeah, that's it

if we can keep the awake handler at this size, i'm fine with false 
at the bottom

Mines a bit long ...

well, see you around

Thanks muchly.

ftp STOR now supported ..

Just wondering .. if we want a graphic file transfer progress meter, 
we need a way to tap into the event handler to catch the number of 
bytes being written/read ...

Also need a way to stop a file transfer that is in progress ...

Is there going to be an approved method of implementing these things?

Or do we hack our own and hope that someone comes along and unifies 
all the schemes

http://www.linkedin.com/ppl/webprofile?vmi=&id=1690833&pvs=pp&authToken=iSCS&authType=name&locale=en_US&trk=ppro_viewmore&lnk=vw_pprofile


Holger's linkedin details ... wonder if someone could persuade him 
to do SSL again but for R3 ?

Small optimization:


Graham, if you try to connect to a host with an ip as a string, then 
a DNS lookup is performed even if it's useless.

On the other side, if you provide an ip as a tuple, no lookup is 
performed and it's a straight connection.


So as an example, when you enter in PASV mode (ftp proto) try this 
instead.

data-address: to-tuple to-block form copy/part tmp 4

so I put the open port where?

you don't need to, the first attempt is the right one

oh .. yeah ... ok. Good point.

you will receive a connect event but no lookup

works

Uploaded latest version with this change, and the STOR command .. 
just in time for bed!

not much else to do .. just delete, create directory, rename .... 
and append to existing file

i just wake up :-)

oh .. and then create the higher abstraction so that it supports 
the R2 of of reading and writing files ...

I just sent you an awake handler!

Anyone else where interested in helping polishing up these schemes?

Graham - we have all world REBOL developers here ... 5-10 ... so 
basically yes, we are interested, just pressed for the time :-)

so the old read-io of R2 ... is it just now read in R3?  Or must 
I know more than that?  I am porting my product to R3, so I am trying 
to get that part figured.  It's almost running now, besides this 
(maybe...fingers crossed)

just read ...

prot-send.r is just a function and not a scheme.  But it relies on 
system objects such as email ...  I guess we can include these in 
the function until some decision is made about where they should 
go.

The lack of TLS and SSL is going to be a big problem since so many 
people now use secure protocols.

R2 2.7.7 has mention in notes about TLS SSL.  My question is what 
is the test case these were tried on?  I just want to verify they 
work in R2.

This is R3 group.