World: r3wp

I didn't try to run cheyenne this way yet.. I needed to explore these 
options .. also the & for some mine server that was running actor 
net. I am using dtach for that and I also have one running console 
for cheyenne now

Good news about the svn

Doc, correct, but your approach works just as well for me. I explicitly 
force word passing because the web context is created in the RSP 
engine for the parent page.

So, RSP is good enough, except we are more API oriented with a Javascript 
front end :-)

Well, I've found RSP script pretty handy for web services too, generating 
dynamically javascript code or XML for AJAX requests.

XML I can see, but JSON is so close to REBOL.

I don't use much JSON, I generate the JS code directly server-side 
(using RSP) and just Eval( ) on client side.

I use cheyenne which generates mostly JSON for one project, haven't 
seen any problems

Does the trunk have the version that allows different webapps to 
access the same DB virtual name but different connections?

Yes it has, just look in the changelog file : http://cheyenne-server.googlecode.com/svn/trunk/Cheyenne/changelog.txt

thanks

Thanks Dock, much appreciated 8)

side note: if you have:
persist [sessions]

in your httpd.cfg file, stop the server and delete the %.rsp-sessions 
file before upgrading to the latest svn version

What's the relationship between vhosts and webapps?

ie. can I have webapps inside a vhost?

vhosts are just containers, so you can have one or more webapps in 
a vhost.

Thanks.

Do vhosts work with stunnel ?  ie. I can redirect incomming https 
to different vhosts?

I've just started testing the latest cheyenne out of SVN.   No matter 
what port I run it on, it always says it is runing on port 80 when 
you hover over the system tray.

I encapped cheyenne.r and now my cheyenne server just terminates 
without any entries in the crash log :(

doesn't look like you can get a verbose trace by default with the 
encapped version

http://pwp.s3.amazonaws.com/checmd090801.exe

is the encapped binary of cheyenne using rebviewcmd encap

Try running the encapped version with -vvv as command line argument.

it just shuts down with no explanation.

1/8-10:32:43.093-[boot] Cmdline args : -vv
1/8-10:32:43.093-[boot] Processed    : [verbosity 2]

1/8-10:32:43.093-[boot] Boot flags   : [no-screen verbose tray-only]
1/8-10:32:43.093-[boot] Data folder  : %./

oops .. another v

now got a crash log

1-Aug-2009/10:34:38-7:00 : make object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'set-modes
    arg2: 'target
    arg3: [file! url! block! port!]
    near: [set-modes sys remote-mode]
    where: 'set-tray-remote-events
]

Same here, but runs ok if I encap from my personal repository, so 
it's maybe caused by an out-of-sync file in the svn repository.

oh ....

would you do a cmd encap?

or checkout from the repository and try encapping again from new 
checkout?

It's ok with enface, but fails as yours with encmdview.

older cheyenne is okay with encmdview

Crash located in %uni-engine.r at this line :

get in new 'on-received

Encmdview chokes on my IN native spec block patching.

oh...

I think it runs okay under rebcmdview though

Hope I haven't ruined your weekend now!

Code path for IN patching differs when running encapped.

No, I've just patched the code to take account on the new encap behaviour, 
just testing it. ;-)

Seems that there's a regression in the LISTEN config option processing, 
fixing that...

Did you notice it gets the port wrong when you hove over it?

Yes, that's fixed. It was working ok if custom port was specified 
from command line (-p option) but not if set in the config file.

Updating the svn...

Done.

I'm trying to run cheyenne on EC2 ...

more problems than I thought I would have

What OS are you running Cheyenne on?