World: r3wp

Just remembering my Cerebrus pop proxy anti-spam script .. I had 
both progress meters for both messages download and message download

yeah, i'm still undecided how to best model that

so some standard way to provide callbacks on data transmission would 
be good

currently we have read, read/part and maybe copy/part in our arsenal 
of avail tools

but overall, i think a more general awake handler would be the way 
to go

well... we can handle this in the event handler ...

but .. we still need a way of defining these so that the user can 
access them.

eg. a user defined on-write callback and a on-read callback

or maybe a user defined event handler that we pass fake events to 
..

real events would be even better :)

I guess the first thing is to try and get them to the level of the 
r2 schemes in terms of user use

If anybody wants to start torrent protocol, here's simple *.torrent 
parser: http://box.lebeda.ws/~rebolek/rebol/torrent.r

:)

that would be awesome  :-)

write read torrent://file.torrent  %file.avi

url is wrong, obviously... but just the idea of it being this simple 
 ;-)

I could use the .torrent file parser now, even before we start writing 
the protocol, to do file management utilities.

Maxim, wouldn't it be open instead of read?

OPEN would assume rebol knows how to decode the binary data downloaded 
by the protocol.. 

can OPEN handle an avi file as we speak?  I don't think so.

You are opening the port, not the file. Torrents are both clients 
and servers. You would probably open a port spec, which would open 
as many sub-ports as needed. Closing the torrent port would close 
the whole torrent session. There would be a flag in the torrent port 
that would indicate whether the file had completed downloading.

Maxim, OPEN works on ports. LOAD is what would require a decoder 
- OPEN doesn't decode anything.

Is someone going to write a torrent:// protocol ...or is this torrent 
noise ?  :)

It's on my list, if someone else doesn't get to it first.

On testing a ftp server behind NAT ( well, it's a home system ), 
the ftp server responds to a PASV command with its local non addressable 
network address.

So, need to ignore the IP address and use the remote-ip address obtained 
on the initial lookup

I don't think my r3protocol-fu is high enough to continue much further 
than this parser :) But I may look at it tommorow bit more, to see, 
what it requires to write a protocol.

well, you don't need to write a scheme ... if you can write it as 
tcp, then it can be turned into a scheme and protocol

a scheme is just a wrapper

Hm, I still haven't experimented with schemes/protocols/anything 
networking in R3 yet, so I don't know where to start.

go on to the wiki, and read everything under ports

starting with a torrent protocol is probably not the first thing 
one should tackle!

Yes, I just did  the parser that may be useful to someone who actually 
know what he's doing :)

What's the parser for ?? Parsing a .torrent file?

Exactly. It returns block!

Probably the idea is to open up a project on codeplex and plan the 
functions needed to support the scheme

Unless Brian really wants to write it all himself ...

:)

Meanwhile my little fix for the ftp server behind NAT has allowed 
me to finally open up a data connection to my fax server

Need a little function

non-addressable: func [ ip-address ][ returns true or false ]

syntax perhaps some like this 


send fax://userid:[password-:-faxipaddress] [ dial: number! retries: 
integer! resolution: word! notify: email! file: file! when: time! 
]

brian: sorry... you're right (open vs load), but if a protocol/scheme 
exists for torrent, read and write should work on it, just like for 
any other scheme, its part of the point of having this whole architecture... 
no?

this could make a nice protocol  ;-)

http://suicidemachine.org/

facebook actually sent them a cease and desist court order!

Is this what we are supposed to be doing?
http://rebol.wik.is/Rebol3/Modules/Mod-network

Graham: Yes. I'd call it mod-net-util, though, in remembrance of 
R2

Ok.... everyone ... please !

I read this last night http://www.tcpipguide.com/free/t_TCPIPInternetMessageAccessProtocolIMAPIMAP4.htm

Seems that there are 3 states in IMAP4, not-authenticated, authenticated 
and selected state.

well, client states

the FSM diagram is here http://www.tcpipguide.com/free/t_IMAP4GeneralOperationClientServerCommunicationandS-2.htm