World: r3wp

Thanks James.

Thanks.

Doc, I'm thinking this version fixed my cookie issue with Curecode 
. We'll see. So far it looks great. Merci.

Good to know. You're welcome.

Anti-web-scanners configurable engine means what?

Complicate expressions to tell you about a request blocking new feature 
with pattern recognition (see Changelog, look for "block").

I presume it's okay to start up cheyenne then load up my modified 
http protocol ?

My RSP scripts do a lot of SOAP and REST calls which use my mods

Sure, you can load your custom HTTP protocol from your RSP code, 
or better, using the new "worker-libs" config block.

so, if used in the worker-libs config block, all workers would then 
use it?

Yes

OTOH, that means each worker needs to load this ... might be easier 
for me to re-encap as the default http protocol

I guess I'm looking for something that is run only the once .. and 
then is used by all the new workers

Workers run in separate processes, so they each have to load all 
libraries one way or the other

However, workers are only loaded once each and then reused, so your 
HTTP scheme will only be loaded the first time.

Ah ... okay.

Same with the worker-libs, that's the point of that facility

Still looking forward to a virtual drive so we can encap all the 
sources for our rsp scripts with cheyenne!

You may eventually compile them into Red

New Cheyenne documentation available: http://cheyenne-server.org/wiki
It covers basic Cheyenne & RSP usage.

Now back to Red! :-)

Just skimmed, but it looks *very* nice Doc.

Thanks Gregg, hope it will be useful to newcomers.

Is it possible for Cheyenne to support SVG?
I tried:
response/buffer: {<svg></svg>}
response/set-header 'Content-type "image/svg+xml" 


but failed.   double string was returned. "<svg></svg><svg></svg>"

You're using a literal string as response, you should try to add 
a COPY in front of it to avoid side-effects: response/buffer: copy 
{<svg></svg>}. Even better, as you're in a templating system, make 
it a template:

<% response/set-header 'Content-type "image/svg+xml" %>
<svg></svg>

Thank you.

good luck with RED. i saw your PDF about RED it will be very impressiv 
 ;-)

Thanks Claude. I hope it will be as useful as it may be impressive. 
;-)

I am trying to use SAY to support EN, FR, and ES.  But only display 
one language.... possible due to wrong HTTPD.cfg.  I think I am following 
this  http://cheyenne-server.org/docs/rsp-api.html#def-33I 
put the  locales-dir %catalogs/ within the App because it was rejected 
in other httpd.cfg locations.   Can anyone SAY what I am doing wrong?

How are you testing the language? Using locale/set-lang (http://cheyenne-server.org/docs/rsp-api.html#def-61) 
or by changing the language in your browser?

Altme just locked me out because I was interrupting your work on 
RED.

I am using the example from the RSP API  - locale/set-lang 'fr

I had also issues posting on AltMe today.

Have you put the LOCALES-DIR directive in a webapp definition?

Yes 	webapp [
	
		virtual-root "/DocK"
		root-dir %www/DocK/

		locales-dir %www/DocK/catalogs/
		debug
	
	]

I tried a lot of combinations .... %catalogs %www/catalogs with the 
.cat files at all levels

Have you restarted Cheyenne each time you changed the configuration 
file?

I don't remember exactly right now but I think when I used cheyenne 
in multilingual I had some problems with this too, and I hacked RSP.r 
(I think) I hardcoded some path to make it work .. it's a while

MikeL: I'll write a small test using the example from the doc to 
see if there's something wrong there. I got localization working 
correctly in CureCode, but that's the only webapp where I used it, 
so unknows issues with paths are not excluded.

Thanks Doc. Keep Red first priority though.

Some other things don't work for me ...  Jobs don't fire as documented.

When I get something working I will document in your Cheyenne wiki.

Try with: locales-dir %DocK/catalogs/

That should be the correct path. Catalogs files must reside in their 
lang folders (catalogs/en/en.cat, catalogs/fr/fr.cat)

Jobs are quite experimental, but should be working in the general 
case (I'm using it on cheyenne-server.org to run a batch script every 
hour).

Testing the set-lang example locally, works ok here. With "locale/set-lang 
'fr" I get:
Bonjour Bonjour nous sommes en Mars

With "locale/set-lang 'en", I get: 
Bonjour Hello we are in March

Is that modeled after Amiga catalogs? The file structure is exactly 
the same in Syllable :-)

Maybe inspired by Amiga at an unconscious level when I wrote it. 
;-)

MikeL: I've upload my testing webapp, you can get it from: http://cheyenne-server.org/tmp/test-lang.zip
And this is the configuration I've used for it:

default [
	...
	webapp [
		virtual-root      "/test-lang"
		root-dir            %www/test-lang/
		locales-dir     %catalogs/
	]
]

Thanks Doc. No luck so far. But will keep trying. I am running Win7 
binary cheyenne-r0920-pro.exe