World: r3wp

Do you mean that sessions are non-working, or that there is something 
about non-working sessions that makes HTTP (a stateless protocol 
that wouldn't normally need sessions) not work?

I don't know what is with sessions. The uniserve seems to pretty 
good to me. I'm using it. And I think that Doc is still Reboling, 
probably just don't have so much time.

BrianH - of course if you don't need sessions, httpd is probably 
working well. I just did not understand the Cheyenne release. The 
simple demo did not work. There is a demo with screen divided into 
something like 4x4 subwindows (frames), and most of them times out. 
Doc told me session layer is about to be rewritten, then no word 
from him for another few months

Surely you are not surprised that Doc would disappear abruptly? He 
seems to have even less time than I do.

there is file %libs/cookies.r so one can take a look at it, if needed

the chayenne is just encrypted uniserve

You mean HTTPS?

I don't know how it's with https, I don't have /command

I don't know how it would have HTTPS server support, even with /Command. 
I thought /Command only has SSL client support.

well, command can read https pages...?

ok... doc' seems to be online now, as he emailed me almost immediately:


I'm aware of this problem (cgi and paths). It's because the encap-fs 
system is not 

correctly supported in this version of UniServe (it's ok in the Cheyenne 

package). I didn't fixed it because, with the release of Cheyenne, 
I'm 

not sure to keep the CGI support for the HTTPd service in the UniServe 

package. I may just provide a static HTTPd server with hooks to extend 

it or embed it in user applications. v1 of UniServe have to be very 
easy 
to embed in any app (that's one of main goals).

Reading is client-side SSL.

Sessions are broken in cheyenne.  Basically session data from one 
client ends up as session data in another :(

Rebol can't do server side SSL ... Carl thought it could by changing 
a flag, but it does not work when it was tested.

So, without server side SSL, Cheyenne can't do https .. unless it's 
thru stunnel.

Rebol can't do server side SSL
 - close but no cigar, actually, it is not that hard

let me rephrase that .. no one outside of RT and their contractors 
know how to do this.

close but no cigar again

:-)

(you can implement it in REBOL)

all the actual core needs are within... its just a question of reading 
the rfc (or implementation guides, or books) and using the encryptions 
funcs within REBOL...  but I'll agree its not for the faint of heart... 
I've read a lot about server-side ssl implemtation a few months ago 
and its quite laborious.  But still doable.

do i smell a competition?

If I had time I would have done it much before, but we ended up using 
apache and a reverse proxy setup... and that works really well.

it also allows us to spread connections over many machines/threads 
virtualise the port and all that nice stuff without actually having 
to code it.

(and apache is good at handling thousands of requests without crashing)

Must say, that I'm all day using the proxy service from the latest 
uniserve and have no problems with it. It's fast enough even when 
streaming videos:) It's quite fun to watch what files are transfered 
while surfing.

hum... uniserve can work as a proxy  ?

yes, and it's the best Rebol proxy I used. Just:
uniserve/boot/with [services [proxy-http] protocols [http]]

The source is in %services/proxy-http.r

hum... and I was just wishing a stable proxy was available in rebol 
last week for some testing... thanks! for the info.

At the beginning I modified it a little bit to better print out urls 
and to save favicon files if found while browsing:)

exactly the kind of snooping I'd add too  :-)

About server-side SSL : after several beers last year in Paris, Carl 
told me that the ssl:// scheme could be turn to work as server-side 
with just the right flag set (IIRC, was about setting the right "direction" 
in encryption), then you "just" have to implement server-side HTTPS 
protocol to support it fully. I've since that, tryed several times 
to get the info about the "magic flag" from Carl, without success. 
So I've prepared several dozens bottles of beer to be sure to get 
the info from him at the next DevCon ;-).

after several beers last year in Paris, Carl told me that...
 oh, so that's how it works! pardon me, I couldn't help it. :-)

so if we bring some czech beers, we can probably get whole source 
code? ;)

Rebolek - that is for sure!

He wouldn't drink Jaime's free beer!  ...

Is there a ftp client for uniserve?

Or, at least an example of a uniserve client copes with using a command 
and a data port.

Not yet, but I would like to add one.

It would require to control a "data port service" from a "command 
port service".

Never really investigated deeply such construction, but at first 
look, I don't see any  issue doing that.

I have somewhere testing script (not for uniserver) working as simple 
ftp server.

maybe I could try to rewrite it

but at this moment have other things to do

I'm looking more for client than server :)

Yes, but if you know how works server, you should know client as 
well:]

off topic oldes, but are your postgres driver fixes folded back into 
the offficial driver ?

Graham, btw., what would be needed for Rebol FireBird support? Does 
it use typical tcp scheme as mySQL e.g.? This week I met with two 
ppl using FireBird, and there seem to be no answer from Rebol part. 
Well, maybe ODBC, but that is not free ...

It has an undocumented tcp protocol .. so for Linux, there is no 
option but to move to something else