World: r3wp

REST: The starting point is to authorize all HTTP methods by adding 
them in mod-static/method-support callback. Then, if Cheyenne doesn't 
choke on them (should be treated by default as a GET, but untested), 
you can write a dispatching RSP page that will basically do a : switch 
request/method [GET [...] POST [...] DELETE [...] ...]. The upcoming 
v0.9.19 release will bring a URL aliasing feature that will allow 
nicer and more RESTful URL.

so people asked for a wiki and then don't contribute?

Load balancing: if you're using RSP, you got it for free as each 
RSP is executed in its own separated process.

I think Brian was talking about using Cheyenne to do load/balancing 
for another application

as a proxy

maybe the one that asked are now too busy...anyway, the wiki was 
a good testbed for enhanced PHP support in Cheyenne.

method-support: func [req][
		if not find [HEAD GET POST PUT] req/in/method [
			req/out/code: 405
			return true
		]
		none
	]

Proxy: it can be done but requires a little more work, like building 
your own mod-something and implementing an async client protocol 
in Uniserve (unless you want to use the built-in HTTP async client 
protocol).

missing DELETE, OPTIONS, and FOO

just extend the method block list with whatever method you need

so, how would one determine if it's a REST request or just a ordinary 
other request?

the restriction on method was done mainly for security reasons (no 
appropriate default handler for other methods except these 4). PUT 
is treated by default like POST.

REST = HTTP request, so it depends on which handler will respond 
to the HTTP request. If your URL point to a .rsp => RSP handler.

Ok.

So, this is very doable then?

So your REST URLs have to point to a .rsp resource.

Well, in theory, yes :-)

I see that Deki uses query parameters on their PUT methods

is that standard?

If you need the HTTP client for Uniserve, just let me know, I have 
a much more recent unreleased version that should work better than 
the old one in Uniserve 0.9.9.

sure ..

I guess that the HTTP method and URI query parameters are not related.

what I read is that parameters are supposed to be sent as custom 
headers with PUT

but I guess that's harder to process

from RSP, you just have to look in request/headers to get custom 
headers.

what do you mean the REST URLs have to point to a rsp resource?

with REST you don't have a static page to point to

for now, if you want that your requests be processed by Cheyenne, 
you have to.

Async HTTP client for UniServe: http://softinnov.org/tmp/HTTP-client.zip

T'hanks.

HTTP.r shoud go in UniServe/protocols/, libs/ should go in UniServe/

Need to go now...

ok, thanks ..

what version of core does cheyenne need?
Will it run on some core 2.5?

I was playing around with core on Win CE and 2.5 I believe is that 
last update...

Cheyenne needs at least 2.7.5. It should work on 2.5 I guess if you 
backport some mezzanines (like EXTRACT) and emulate some natives 
(like UNLESS). You also need CALL or LAUNCH in order to support RSP 
and CGI scripts.

Cheyenne 0.9.19 Preview Release : http://cheyenne-server.org/tmp/cheyenne-r0919.zip

This release hasn't been much tested, that's what I've called it 
PR. I'll make the official release in a few days.

Main changes are :
- an improved PHP support (now works reliably)
- sandboxed RSP webapps (as much as it's possible in R2)
- now compatible with REBOL 2.7.6
- bugfixes

See ChangeLog.txt file in the archive for complete description.

Watch out for regressions in your RSP webapps that might be caused 
by the new RSP sandboxing system. For those having a server in production, 
test your RSP applications carefully before upgrading.

hi doc, where can I find the syntax for the alias modul? (I wan't 
create a directory - cgi - alias)

ALIAS /url-path %filename (%filename can't be a directory)

thx doc, but what if I want to access cgi's in a directory 'outside' 
the document root?

Cheyenne serves content only from the document root.

But nothing stops you to use wrapper CGI to execute REBOL code outside 
of the document root (using do %...) if it's really required.

to use => from using

thx for the info

Btw, why bother with CGI scripts when you can use RSP script which 
are far more powerful ?

Anyone got the lastest distro working?  Mine just hangs on do %cheyenne.r

very odd ...must be something to do with Vista ... the cheyenne.exe 
works fine on XP, but does nothing for me on Vista.

Anyone got Vista working?