World: r3wp

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 :)

I'll buy you more memory. :-)

I won't complain though. Your code is excellent. Clean and easy to 
read. Very nice.

more time, please :)

it's rather about quick typing, than about saving memory :)

(thanks)

You must be a very slow typist for those chars to add up. ;-)

has what i consider now to be a really stupid overloading of READ, 
though

There are definitely time in REBOL where things get overloaded and 
the context is hard for humans to deal with.

Schemes are one of the areas where I think you need to internalize 
the model of port, sub-port, actors and events to really "get it".

Then you can write a scheme. :-)

Andreas, on linux what do you get for this ?
>>? :system/ports/system/awake

same as in win32

problem is, there's no event device on linux yet, whereas there is 
one on win32

that's why with linux r3, a simple "WAIT 10" will happily consume 
100% of one core for 10 seconds

bad

yep

so, here's a first update: http://bolka.at/share/prot-pop3.r[temporary 
url]

A remark. You don't need to convert string rules into binaries when 
you parse a binary

where?

when you parse CRLF for example

bom and eom

the can stay as strings

*they

that's gone in the recent rev anyway

and at least for FIND that's not true

in the PICK actor, I yet see them

refresh, then :)

ouch :-)

Andreas .. regarding IMAP4, I looked at the RFC and then revised 
RFC and then the corrections to the revised RFC .. and I thought 
.. maybe it's going to take some time to read!