World: r3wp

Looks like AIM still has free IMAP ... signing up again!

Signed up, sent myself a couple of emails to that account, and then 
managed to login and download using the imap protocol

Graham - you are becoming a networking Guru :-)

Nah .. this stuff isn't at all hard.  Carl made scheme creation much 
easier than in r2

I suspect that the amount of detail put into making a bullet proof 
http scheme frightened everyone off!

yes, probably ...

Any thoughts on the unification process of error handling, logging, 
timeouts, etc.?

Well, Carl is going to have to look at them .. but since my  schemes 
use the same method ... they are pretty unified :)

So, where's the best place to start... the one that best shows the 
basic template?

smtp I think ...

though that one is an early effort

So, not Daytime?

Graham: During your "journey" through this .. did you notice if there's 
a standard template that would make sense for various parts of the 
implementation?

Also, where and how would you like to see my comments?

I started with daytime, moved to smtp, and then ftp, fax and now 
imap.  I am using pretty much the same template with changes appropriate 
to the protocol.

I think docbase ... is the place

Daytime is too trivial to learn much from ... maybe FTP instead??

Ok.


My question above is whether there's a standard "core" that can be 
used across many protocols... a bit like net-utils or default protocol 
on R2.

I'll go with SMTP for now.  Looks simple enough.

The only standard stuff I use is ...
1. net-log
2. some parse rules and bitsets
3. some authentication stuff like cram-md5


I also stack the commands sent to the port and pop them off as the 
port is async ...

I do this in ftp, fax and imap .. but I should go back and do this 
for smtp as well

I was thinking of using net-log as a way to hook into the low level 
activity of the protocol so that I can patch it as needed when interacting 
with a GUI ... eg, for progress meters

Ok, good... then I'll start with IMAP... since it's more recent.

One thing that is not clear to me is that if you write to the port 

eg. write imap-port [ dialect stuff ]

and then 
wait imap-port


it can return immediately ... and you don't get anything unless you 
put in a timeout

eg. wait [ imap-port timeout ]

Ok, let me upload the latest version ....

Isn't that dependent on what you return from awake?

in wrote there is a 'read port .... but i don't get anyting back 
without the timeout

uploaded 0.0.3 

can login, select a mailbox, get length? and pick

It's at the bottom of the page as a file attachment

BTW, nice use of Deki wiki.

It looks pretty but is slower than docbase :)

and there's no REBOL formatting .. so I use ruby or whatever ...

Runs really fast here. Where's the server?

I think EC2

It was a free hosting offer I picked up a couple of years ago ...

That is Mindtouch were offering free wikis to people limited to 200Mb 
I think

Of course what I really like about it is that there is a REST based 
API that I can use with REBOL.

Carl - guys found out, that we have just one shared buffer - why? 
You have to read everything out during read phase, or you can get 
corrupted data ....

pekr, what protocols are full duplex?

none ... but wasn't it you, after all, who just wondered, why the 
in-out buffer is shared?

No .. I just pointed it out.

And wondering if that imposes a lot of GC ...

It's one of those things that's in the "balance".

It turns out, I think you can allocate separate buffers, but you 
must know how to do it... and I've not tried it yet, so have not 
mentioned it either.

But, I did give full duplex consideration during implementation. 
 I think more modern IM systems benefit from it.

Also, it turns out that one must be careful when estimating GC overhead. 
Sometimes it is more efficient, becuase otherwise you must add extra 
code to manage memory usage... that is constantly being run. You 
know what I mean?

It wouldn't be a big change to the schemes if that gets implemented 
right ?

Right. No change to schemes.

lunch time, bbl

I think in my ftp scheme I access port/data directly so I can stream 
to the file system .. so it would require a tiny change if there 
were two sep buffers