World: r3wp

He used to work for Rebol Tech, and did the SSL implementation ... 
and prior to that was an Amiga networking guy

Ah.. Now I remember.. Some (many?) years ago people were trying to 
reach him so that they could register his net stack and get keyocdes.. 
(or ask him to release it free if he's not willing to sell it anymore).. 
AFIK neither happened.. Luckily there are some new (PPC) native stacks 
available.

Yep , that was him.

Btw.. he was wrong about using Xon/Xoff instead or HW handshake.. 
 those are used even today  and If I had to choose one Id' definitley 
go hardware. keeps the serial line pure 8.bit, and workd more reliable 
on multitasking PC:s...

Looks like we do have TLS after all ... :)

Did you test the code?

>> rebol/version
== 2.7.7.3.1
>> smtp: open/lines tls://smtp.gmail.com:587
>> set-modes smtp [ secure: true ]
** Script Error: Feature not available in this REBOL
** Near: set-modes smtp [secure: true]

Hmm... not working.

I'll post a comment to his blog ...

Hmm.. Where those SSL and TSL should be?  When I look:      ? system/schemes 
   it does not show those at all..  there is HTTPS though?

this works though 

>> smtp: open/lines ssl://smtp.gmail.com:465
>> set-modes smtp [ secure: true ]
>> close smtp

>> pick smtp 1
== "220 mx.google.com ESMTP 39sm6677160yxd.27"

Are you using /Core or /View?

rebview

Same failure under R/command

Well, CureCode it when you get the chance, or if you are impatient 
RAMBO it and it will get migrated to CureCode later.

http://rebol.wik.is/Protocols


I made the two - three line changes to prot-smtp.r and prot-send.r 
and uploaded them here.

And using 'ssend was able to send email thru gmail using ssl .... 
for those that asked.

Probably better to use a refinement ... like send/secure .. or something.

But that will get people going who want to use gmail to send their 
email ...

Thanks for the link, we'll look into it.

Joanna, there aren't a lot of docs on serial ports, but the basics 
are easy enough.


; port speed data-bits parity stop-bit (order is not significant 
IIRC)
port-spec: serial://port2/38400/8/none/1

p: open/no-wait port-spec

p/rts-cts: off  ; THIS IS REQUIRED TO TURN OFF HARDWARE HANDSHAKING!
update p

Then you can just INSERT and COPY on the port.

Graham, what are some of the "tweaks" you made to Http that BrianH 
has mentioned for inclusion in the next R2 release?

http://rebol.wik.is/Protocols/Http

You can confirm that it does what it is supposed to do by looking 
at the http traces.

Doc in the Core group: "this could be a really great addition to 
R3 (or even R2)"


Policy: Additions of new globally defined functions to new R2 releases 
almost always must get put in R3 first, go through consensus, testing 
and the REBOL optimizer, then be backported to R2 (usually through 
R2/Forward). Enhancements of existing functions in comparable areas 
of the code (not ports, View or library) also go through the R3 gauntlet 
first. If you want R2 /Core enhanced, get to work on R3.


Change to the semantic model of R2 isn't going to happen: No new 
port model, no new View, no extensions or host code - use R3 if you 
need those. New (real) R2 datatypes are unlikely, though faked backports 
of R3 datatypes are OK and have already made it into 2.7.7, with 
more to come. Natives that can be fixed without changing the semantic 
model or adding new datatypes are fair game though.


Bug fixes will be done though as long as code (that we can't fix) 
doesn't depend on the bug (no fix to PICK, POKE and AT's off-by-one 
error, for instance), as will backwards-compatible enhancements to 
R2-specific areas, like the port model, View/VID and library support. 
Backwards-compatible means we also test it against existing code, 
so if you want to test it against your favorite code, please do so 
and tell us what you find.


These fixes are coming, at least in theory - someone has to do the 
work. If you have a favorite bug you need fixed or enhancement you 
need, do the work yourself or pay someone to do the work (REBOL Consulting, 
perhaps). Changes go in as they are made, and they are made by people 
with priorities. If you have priorities too, act on them :)

If anything we do breaks your code, *please tell us*. We really don't 
want that to happen. Backwards compatibility is a top priority.

This is my attempt to link to the wiki docs

http://rebol.wik.is/Man

so,

man //

WIKI:
    http://www.rebol.com/r3/docs/functions/z-q-q.html

It's a hacked 'help ....

oop s.. that should be 

man ??

This assumes that the docs will be fixed .. currently  < maps to 
-gt and > maps to -lt in the docs.

Maybe someone can improve the parse rules for me

man -> help/doc

in R2?

An enhancement to an existing function that is compatible with R3? 
Absolutely, it will be added.

Totally within the rules :)

just need to get Carl to generate r2 docs in a similar location

Right. That's part of the the plan for 2.7.8.

I loaded the new REBOL/View 2.7.7.3.1 1-Jan-2010 down and tried to 
run it without installing.

It just writes a bypass-install file with true in it, but it does 
not run.

However starting it with the option --noinstall still works as expected.

Noted.

Have I read the blog correctly ? SSL ODBC and encryption added to 
REBOL/View Standard ? This is a nice news !

Indeed, a "YAY!" is in order :)

What is a YAY ?

A cheer. Your team just won, Yay!

I have to use 


call/show "cmd" to see the shell .. is that the expected behavior 
these days?

Yes.

That was a 2.7.6 change Graham. It bit me, so watch out.

Yes, I knew that and I wondered if we were going to revert back to 
the 2.7.5 behavior.

My recollection was that it was always just call until 2.7.6 ..

I campaigned to have it changed when it happened, but I think I've 
ported all my active code to the new syntax now, c'est la vie.

me too