World: r3wp

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!

I haven't used IMAP4 for years so ... for me it's going to take time 
to get up to speed again.

Also just looking at your code ..  my understanding is that if you 
request a message, you have to keep reading until you hit a  crlf 
".," crlf  sequence ... but I don't see that anywhere in your code.

crlf "." crlf

the most recent version doesn't currently fetch messages, yes

going backwards :)

most definitely :)

How would you suggest I approach the issue I raised above?

viz. Sometimes you want to exit from the handler after a messsage 
and sometimes you don't ...

Hm, could you be a bit more concrete? Give an example for the kind 
of write, maybe?

Maybe I'm wrong .. and you always want to return true after some 
data is returned

I'll work on that assumption :)

ok :)

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