World: r3wp

ws protocol works,
run the chat server (see the post on the forum)
p: open ws://localhost/chat
insert p "hello"
pick p 1
== "hello"
insert p "/nick endo"
pick p 1
== "server: you known as endo"

and pick p 1000000 is the same?

I guess so :)

some ports a pick is a bit meaningless

yes, you can use only pick port 1.

if no data, then it returns none, so you can simply poll it. it doesn't 
wait for the data.

ws protocol is event based in its specification, so made it as no-wait. 
then and event based protocol can be built on this.

syntax highlighted version http://www.moldibi.com/rebol/ws.html

net-utils/net-install ws self 80

Endo, for the moment, use 4 spaces for tabs, and you're formatting 
will stay intact.  I'll change the script to replace tabs with spaces.

Endo, I updated to script to maintain formatting in a few new ways 
:)

Thank you Nick.

I know you can run virtual sites on the same port .. but do things 
work better if you run an instance of Cheyenne for each site ( using 
a different port  ) ??

At present I have to manually edit the httpd.cfg and restart ( maybe 
reloading works ) Cheyenne when I add a new user.

I'm wonding if I can just create a new httpd.cfg from a template, 
make the changes to support the port I want to provision, create 
a sym link in the new directory and then run from the sym link...

Graham: why do you need to edit httpd.cfg for each user?

Also, you can reload the configuration without restarting Cheyenne

The Syllable Server manual has an example how to do that on Linux:

http://web.syllable.org/Server/README-SyllableServer.txt

Janko, because each user has their own domain

Is there an equivalent for kill on Win32 ?

I was thnking of using a web socket connection to cause Cheyenne 
to reload its configuration

Graham: domain or maybe subdomain? if subdomain and maybe domain 
also you could probably put nginx in front of cheyenne and use rewrite 
rules to do this (depending on the concrete situation)

Domain ... not subdomain

Maybe that's what I should have done in the first place ... used 
sub domains :(

And that way I wouldn't have all the issues of mismatched ssl certificates

for subdomains it's simple (and much cheaper than domains, since 
you don't have to buy each one) .. you use rewrite rules and modify 
domain to a get parameter that cheyenne can act on

I think so called wildcard certificate work on all subdomains

I mean, you buy one for all subdomains

I don't buy the domains ..the users do :)

I don't have that many users .. .so maybe I should start again ...

Who do you use to manage your domains?  Godaddy?

And is it easy to redirect subdomains to other ip addresses?

if you have nginx in front you can have cheyenne servers reverse 
proxied to many ip-s yes.. in the same way you can for different 
subdomains or domains  (rule for reverse proxy is very simple)

I can send you example if you don't find it on net

I don't have nginx running ... it's a windows2003 server

you also get easy https support with nginx if you need it some day 
... what do you need certs now?

I don't know how stable it's supposed to be but nginx runs on windows 
too now.. I use it here for dev

So, one certificate will work across all subdomains?

I think, if I understood the "wildcart domains" correctly .. they 
are more expensive than ordinary

== "wildcard certificates"

Single Domain with Unlimited Subdomains (Wildcard): $199.99 https://www.godaddy.com/ssl/ssl-certificates.aspx

http://www.comodo.com/e-commerce/ssl-certificates/wildcard-ssl.php

expensive

$800 for a certificate

godaddy-s option is cheaper

yeah ...

well, it depends on the number of subdomains, if this is worth it

I might experiment first with a self signed wild card certificate

Is there an equivalent for kill on Win32 ?