World: r3wp

because the system actually self-identifies its available interface, 
we could even generate the SOAP xml schemas automatically, as in, 
totally dynamically.

So, all I have to do is provide the WSDL ?

and it creates the soap services for me :)

actually, you just provide the code and the WSDL would be built for 
you :-)

the otherway suits me better .. that way I can use someone else's 
WSDL

yeah, but you still have to put the code behind.   the web-api mod, 
provides an interface automatically based on what is actually being 
served.  you could easily build a little WSDL to REBOL api file converter. 
 just load the XML, extract the methods, the parameters and build 
an equivalent rebol function stub.


Then all you'd have to do is implement the function body....  the 
only detail is the xml datatype which don't all map 1:1 within rebol, 
but that can usually be pretty well cornered within the code itself.

maybe even just provide a little PARSE rule which provides input 
validation representing the given schema.

anyhow... for now SOAP is a larger beast to tackle and I'm more concerned 
with REST stuff right now, but since the system will be working and 
you can easily extend it, there is nothing stopping you from building 
the SOAP interface.

(if you need it before I can tackle it)

what is the most trouble free linux to run cheyenne on?

I've never had any issues with ubuntu that I couldn't solve

except

how to start Cheyenne automatically ...when linux starts up.

maybe Someone here knows how?

For me, the most trouble free Linux to run Cheyenne is Syllable Server 
:-)

For autostarting (and shutting down) you have to hook into the init 
scripts, which are very different between Linux distributions. I 
remember having trouble with finding a straightforward way on Ubuntu, 
too

This any help? http://embraceubuntu.com/2005/09/07/adding-a-startup-script-to-be-run-at-bootup/

pwd

Oops, that was meant for my terminal

Cheyenne revision 134:

- FEAT: new config option (globals section): 'allow-method. Extends 
allowed HTTP methods.

- FEAT: -w command line option extended to allow to specify an additional 
"start" number value.

- FIX: -w 0 now starts Cheyenne with no workers at all (was spawning 
one at start until now).
- DOC: updated %changelog.txt (was lagging behind a bit).

See %changelog.txt for more info.

Linux binaries r134 should be available in an hour at: http://cheyenne-server.org/download.shtml

Cool, thanks!

I still need to add some documentation to the wiki for .r file handling 
in RSP context and to mention the new cgi-conf script (from onetom).

what does Database C drivers: MySQL 3,Oracle 8 ... mean, btw?
it doesnt work with mysql 5 and ora 10?

Those drivers are built in REBOL/Command. It depends if Mysql 5 and 
Oracle 10 servers are compatible with older drivers. I can only answer 
for Mysql, and the answer is no.

so what's the point supplying those builds, only the https support?

or why not if u can anyway?

Not everybody run on Mysql 5 and Oracle 10, so it can be useful to 
some users. Also it's all or nothing, I cannot chose which native 
feature I want to include or not.

The ODBC driver and the SSL support are worth it.

makes sense, thx for the explanation. it just looks a bit lame to 
talk about mysql3 in 2011, isn't it?

I should maybe remove that mention from the download page...I agree 
that it looks a bit odd now.

I've upgraded Cheyenne to the latest binary, r135

It recognises the fast-rebol-cgi keyword in the globals now, but 
it doesn't seem to do anything. It seems to try to execute REBOL 
code as real CGI. It tries to use the shebang line and has permission 
problems with CGI files that it didn't have before

Thanks for the report, I will test it locally later today.

having issues starting the cheyenne server from win. it doesn't find 
the system libs.


 I had a fix for the same issue in some other code I did... I'll try 
 to see if this cures the bug in cheyenne .

What do you mean by "system libs"? kernel32.dll?

it turns out it was a different problem... he was running core.  
 but the proper way of loading libs (and I've had to do it to make 
it work on 64 bit systems)

system-libs-root: rejoin [to-rebol-file get-env "systemroot" %"/system32/" 
 ]

kernel32: load/library join system-libs-root  %kernel32.dll
user32:   load/library join system-libs-root  %user32.dll
advapi32: load/library join system-libs-root  %advapi32.dll
shell32:  load/library join system-libs-root  %shell32.dll
iphlpapi: load/library join system-libs-root  %iphlpapi.dll

I was using the simple setup you are using and it woudn't work in 
all people's windows system... the above does work in all windows 
machines.

I never tested it on 64-bit Windows, but I find it a bit odd that 
Windows can't find the system library by itself. It is supposed to 
search automatically in all default system folders.

Also, IIRC, that is the first time someone mentions such issue, and 
I am pretty sure that several peoples here already tried it on 64-bit 
Windows.

yeah, it should but it doesn't it seems  ...  the code resulted from 
feedback when I shared the windows-chrono.r lib on rebol.org and 
a user reported failing lib loading.

Confirmed, I'm running cheyenne latest .exe on Win7 64bit w/o any 
problems, .dlls just load fine.

The "system" folder is searched in all cases: http://msdn.microsoft.com/en-us/library/ms682586, 
there is no way that a call to LoadLibrary( ) (== load/library) could 
miss kernel32.dll or other system DLL that Cheyenne relies on (unless 
the user system is seriously corrupted).

Max, where's this web services plugin?

I'm at the client right now, doing last minute changes for his own 
uses.

I'll be putting a demo server on-line probably later tonight.

as well as all sources and docs as a .zip which simply appens to 
the cheyenne folders.

so you running as a local service?

the default setup is set for localhost, but it can run online, just 
set it up in one of the vhosts you are serving.