World: r3wp

yes, exactly but without the word odbc :)

btw, the cpu load was ~50% over all cores for approx. 5 sec. on an 
ubuntu dektop 8.10 running also 2  vbox vm's.

Interbase have a developer release that is multicore aware.  I'd 
be interested to test this once you do the first release.  The developer 
release is same as the commercial one but stops receiving new connections 
after 48 hours.

Firebird can only use one core.

interesting, will try this one. yes you are right multicore support 
makes sense.

if you like firebird you should also take a look to frontbase. running 
well with windows if you prefer, similar small footprint concept, 
but all in. replication, clustering, embedding etc.
there is also a streamline cli (sql92).

easy to integrate frontbase to the cli connector. one strength of 
this concept.

I use Firebird because I am used to it!

maybe we should shift this to DB

Your work sounds very cool Tomas. I'm sure Graham will give it a 
good test and report back. You may have a lot of people interested.

BTW, I made a couple of tiny changes to prot smtp, pop, and send 
to allow them to work with SSL.  Should these also make it into 2.7.8 
??

Sounds good to me. Which services/variants do your changes work with?

the ones I mentioned ?

Yup.

Yes.

No, I mean the server-side services, official protocol specs, etc.

I don't understand the question then.

You did the client-side stuff, but iirc those particular protocols 
aren't implemented very consistently between services, particularly 
with SSL. Which services have you tested your clients with? Gmail?

Gmail and hotmail

OK, cool :)

that covers 99.9% of the world's email services

http://rebol.wik.is/Protocols

and pop3 http://compkarori.no-ip.biz:8090/@api/deki/files/560/=prot-spop.r

I've got a demo script somewhere that logs in to hotmail/gmail and 
downloads all new messages and strips out the attachments

Found it http://accessories.s3.amazonaws.com/hotmailer.r

Is it Gmail-style POP3 over TLS on port 995, or is it RFC2595 STLS 
negotiation?

It might be a good idea to have the standard pop:// protocol do the 
STLS negotiation, and have pops:// do POP3S like Gmail.

That way we can support both.

Same with imap:// vs. imaps://.

I keep thinking that rebol doesn't do tls ... but if it does, I don't 
use it

I meant your fixes, not what REBOL does now :)

Well my fixes are just to open the secure port ... that's it

Ah, pops then. spop would be pop over ssh :)

pops it is then

what's secure smtp ?

smtps ?

Yes.

Ok, I didn't know the naming schemes

so ssend => sends :)

S in front = SSH, S at the end = SSL. SEND/secure :)

We can add RFC2595 TLS negotiation to the regular pop:// and imap:// 
protocols later.

I doubt it

You doubt that we can, or that we will?

latter

Carl is not after major enhancements to Rebol except as rebol3

Well, it depends on priorities. These changes are mezzanine, and 
just extensions at that, backwards-compatible. Carl doesn't have 
to be involved with mezzanine R2 changes - that's my job.

and probably, the algorythms, once understood can be readily retro-fitted 
to R3.

but TLS is not mezzanine ...

Over SSL then.

And my major priorities that have been keeping me away from my computer 
for the last few months are near their end.