World: r3wp

read returns a binary!

bu you could return a block if you wish ;-)

Ah, so this is a native READ, not a wrapper in your scheme. Got it.

i could return all messages in a block, yes

i think i got the idea of READ iterating from some R3 example

Andreas, where is your source, is that free ?

Then we need a callback mechanism for progress, if we read all in 
one shot.

http://bolka.at/share/prot-pop3.r

[temporary url]

not yet licensed

not need of a callback, you can return a block and populate the same 
block further.
You see what i mean ?

interesting idea

I'd like to see it stay low level in the scheme, as Andreas has it, 
and add wrappers for higher level operations.

yep, i think so

we can add a series protocol later on

the source avail at http://bolka.at/share/prot-pop3.rcurrently still 
has a series interface

length? for getting the num of messages avail, pick for reading a 
specific message

I think I understand Steeve, but then how does your calling code 
know the block has been extended, without polling?

and read for the whole block (which can be updated)

Greeg, i think we could add some info in the block, like a timestamp 
at the head

hm, that'll get messy soon

perhaps it's better to return an structured object

The ability to get just headers, number of messages, etc. is great. 
Get a little info, show the user, request more data as desired, and 
show progress for lengthy ops.

progress for length ops still is an open problem

i could enable copy/part for downloading large messages

Still, without a callback or notification of some kind, the caller 
has to poll against the block to check for changes.

Having the basics first is great Andreas.

ah, i know where i got the idea from. the large file copy example 
on the "docbase" wiki

http://www.rebol.net/wiki/Port_Examples#Copy_a_large_file

ha! read/part :)

Andreas, your binding in the awake function should ne done only one 
time, at construction

sure. but forget that code, i'll put up something more up-to-date 
soon

Yes, I think that should work. Then your state machine will need 
to know it's building a message, or loop internally.

All the recent scheme work makes me want to jump in and see if we 
can make a nice scheme dialect. :-)

Agree

i intend to iterate POP3 until i consider it to be a good example 
for a basic scheme implementation for an "interactive" (lock-step 
request/response) protocol

i think we can then extract a dialect or at least some helper functions 
from there

pop3 is good starter, not too complicated

Agreed. The simple protocols help us identify the foundation elements.

we could give a try for real time collaborative work and update the 
code in a shared sheet. There some tools for that

too little code :)

prot-pop3.r is 113 lines atm

but it's in a git repository anyway, i could share that, if someone 
wants to collab

I'll leave it to you guys for now. I need to make time before I'll 
add much value. I agree with Andreas as well. Better to have him 
complete his vision on this I think.

precisely it's shorten, I think that is an advantage

but that means i edit all over the place, which i think is anti-usage 
for collab editors

What is the @@ for in comments?

those are TODOs

Why not say TODO then? ;-)

two characters less :)