World: r3wp

Mantis is far more advanced bugtracking tool than Trac.

ok

Probably a stupid question, anyway, how to change the port to something 
else when running the cheyenne.exe ?

I think if you want to change the port...you have to use 'cheyenne.r' 
instead.

just change the port-id in HTTPd.r and double-click 'cheyenne.r'

there's a -p command line option to set the listening port (80 by 
default). Example: cheyenne -p 8000

I see you plan on supporting SSL... is this in any way functional? 
or should we simply do a reverse-proxy through apache for now?

(even if it depends on pro/sdk license, btw ?)

Strange quesiton...does Cheyenne do PHP?  Don't ask!  Also, which 
version of core/view is required.

It could probably call php as a cgi, but I don't think it's designed 
for such a purpose. And about version - the latest available are 
probably the best.

I would not use view for server

I'm not sure, if you can run it from Rebol/Base, you may try it.

Maxim: I plan to support SSL natively in REBOL. I'm waiting for Carl 
to send me a test version of /Command with server-side SSL enabled. 
In the meantime, I recommand using a SSL proxy rather that Apache. 
See STunnel for example.

The SSL support will be available only in Cheyenne binary releases. 
You'll need a /Command or /SDK license to make it work with the sources.

Scot: Cheyenne can interface with PHP using FactCGI. A FastCGI client 
alpha implementation is currently built in Cheyenne. All you need 
is a php executable compiled with FastCGI. I've already tested several 
php apps (even big ones like eGroupware), it works well and it's 
fast ! But, the configuration options are currently hardcoded in 
Cheyenne (need to export them in config file) and there's no dynamic 
php instance management (you have to launch each php-fastcgi server 
by hand). Once these 2 feature will be integrated in Cheyenne, you'll 
be able to run easily and php application.

Scot: REBOL/Core 2.6x or View 1.3.x are ok for Cheyenne. Avoid the 
experimental async REBOL kernels.

is FastCGI.r usable separately as a free fastcgi protocol for REBOL, 
or does it work only in terms of Cheyenne?

Oldes: View can be a good choice for server is you need server-side 
dynamic image generation or manipulation. The drawback is for Unix 
servers, they'll require X libs to be installed.

Pekr: The protocol is not specific to Cheyenne, but you'll have to 
"extract" it from the module to be able to reuse it. But, we're talking 
about a FastCGI CLIENT implementation, and what you have in mind, 
I guess, is a SERVER implementation (like in /Command)...

so how does it work then?

run easily and php application
 = run easily any php application"

It supposed to work almost the same as mod_fastcgi for Apache.

It connect to a server application, like php-fastcgi or a REBOL FastCGI 
server built with /Command, or any other server accepting FastCGI 
clients. Then it sends the HTTP request and wait for a response back.

The trouble is with Windows, we still have no-solution. Command Windows 
fastcgi was never fixed - 'external mode is pretty useless

ok, the trick is to use Cheyenne plus Rebol instead of apache, so 
who needs fastcgi :-)

Doc: there is a SSL serverside command version (I know bcause I can 
see it...somewhere) so you should really push it.

On windows, a 2.6.2 Command version, no encap

Pekr: Exactly !

Marteen: Carl told me about some flags to set properly in the ssl:// 
port to set the direction : server to client.

I still don't have this info.

You've made my day Nenad, thanks.

stupid question, just so its obvious... will cheyenne remain open 
source indefinitely ?

Sorry if this question has been asked before, I do not know... can 
you give me an idea of capacity of the server?  will it scale to 
thousands of connections or is it limited to hundreds (or less).

Doc: I have pinged Carl on the SSL channel on another (very private) 
world.

With the four and sixteen RSP demo, getting the following error  
 script error !
Invalid path value: hits

maarten, thanks, I'm needing it too.  if cheyenne can handle big 
loads, and SSL, there is a good chance I'll try to use it.  The release 
commes out at a really good time for me.

Hope it gets faster to 1.0.x then the mysql driver ;-)

I've been using Cheyenne for the last couple of years.

I've not had any stability problems.

Doc: why not bundle mysql:// with it as well, and add a couple of 
CGI/session/cookie libs?

but nor have I subjected it to any heavy loading.

Have you tried any benchmarking Graham?

Nope.

I just use it for webmail.

hmm, my Rebol is getting rusty.

http://www.compkarori.co.nz:8001/index.rsp

source for each of the rsp pages is at the bottom of the screen

userid: test password: account

Open source: I see no points in getting it closed source. It will 
remain open source (BSD). And I hope that once 1.0 is out, that developer 
will contribute to bring new modules and extend it capabilities.

never got round to writing the code to send mail .. so it just receives 
mail.

thanks doc... just wanted confirmation of what I expected.