World: r3wp

The json data has to be from the same server as the source web page

You need to use JSONP for cross site scripting

Additional Notes:

Due to browser security restrictions, most "Ajax" requests are subject 
to the same origin policy; the request can not successfully retrieve 
data from a different domain, subdomain, or protocol.

Script and JSONP requests are not subject to the same origin policy 
restrictions.

Anyway, we are now off topic for Cheyenne

Sorry, I thought it might be a cheyenne issue...i'll move to javascript 
group

Longshot here .. but has anyone written a code formatter for RSP 
pages .. so that it correctly indents HTML, JS, and Rebol all on 
the same page??

there's a php pretty print here http://beta.phpformatter.com/

That's one reason to write as little code as possible in templates

Graham:  I am happy using Andrew's ML.r with Cheyenne to implement 
Don't Repeat Yourself on the few pages that I do. <%

 include %ml.inc  ; does [%pop.r %push.r %build-tag.r %ml.r] which 
 can be pre-loaded 
	print ml compose/deep [
		h1 "Heading"
		p {Text paragraph}
		p (now)
	]
%>

Cheyenne's ReBorCon presentation now also available in PDF format. 
The files used for the webapp coding demo have been published too: 
http://cheyenne-server.org/blog.rsp?view=25

Thanks, Doc!

thanks you ;-)

Cheyenne reached a new milestone, as promised during the ReBorCon, 
0.9.20 is out! 

Read the announcement here: http://cheyenne-server.org/blog.rsp?view=26

All the new binaries are built using REBOL 2.7.8, enjoy!

The web site has been updated too, new documentations for Cheyenne 
are pending (will be available tonight).

Doc, thanks. Can you check the Window's binary links?

Broken links, fixing that...

Done.

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.