World: r3wp

From http://cheyenne-server.org/wiki/Config/Struct:

Note that the embed module, if activated, will disable all the other 
ones (required for proper working of embedded mode).

So far, that's I don't know either :(

Hi Maarten, been quite busy these last days, nice to see you back 
in REBOL world.

About your question: Cheyenne has its own built-in preprocessor for 
encapping. So you should be able to encap Cheyenne using just an 
#include %cheyenne.r

But you need to run Cheyenne from sources at least once to force 
the generation of the %.cache.efs file (result of the preprocessing).

About %httpd.cfg file, it will be written down on disk if not present, 
so if you want to avoid that, you need to patch the sources. For 
that, just edit %Cheyenne/misc/conf-parser.r and comment line 69:

        ; write file data

I never tried encapping Cheyenne in embedded mode, so you might encounter 
other issues though.

Ah, another important thing for encapping: you need to edit %Cheyenne/encap-paths.r 
and configure the paths to your local SDK folder.

OK, I may take a look. What I eed is a really simple web server, 
so if it takes too much time I'l just do a 10-liner. That's good 
enough in this case.

If you need a really simple one, they are several on rebol.org that 
could work for you, like Carl's micro web server script.

back to my problem from april 19th: is anyone using webapps under 
a virtual host?

I have tried to use the testapp on Dockimbels request, but it serves 
only non-functioning rsp pages on http://hmkdesign.dk.

Henrik, if you haven't solved yet your configuration issue, you should 
send me your working directory archived along with your configuration 
file, so I can see where is the issue.

Unfortunately that woud take a while to pick apart as I have other 
pages running on that server.

The testapp script makes this error:

22/6-21:54:04.832205-[RSP] ##RSP Script Error:

        URL  = /show.rsp
        File = /home/henrikmk/sites/testapp/show.rsp


        ** Script Error : empty? expected series argument of type: series 
        port bitset
        ** Where: rsp-script
        ** Near:  [either empty? session/content [
print "<LI>No session variables</LI>"
] [
foreach [name value] session/content [
print [<LI> <B> name ":" </B> mold value </LI>]
]
]]

Are you overwriting 'session word somehow?

Strange error, having a quick look in RSP.r code.

A session has not been started, which is not possible if it's in 
a webapp.

Is this not the same as if app-init.r was never run?

it's the same as for my webapp. app-init.r never runs, when it's 
inside a virtual host.

The session is controlled from the main process, the %app-init cannot 
interfere on session/content loading.

What Cheyenne version are you using?

a fairly late one. I upgraded shortly before april 19th.

There is following tweet of Rebol Tutorial. Any advice?

rebtut rebolution is fun

rebol cheyenne works on IP only http://88.191.118.45:2011/ not on 
domain name weird http://reboltutorial.com:2011

He probably has not configured properly his virtual host.

Does anyone has implemented %html.r extract from Magic! (from Olivier 
Auverlot) under Cheyenne ?

Does anyone is using QM from Chris RG under Cheyenne ?

What are the contribution to Cheyenne ?
Service by Maxim...

I used QM with Cheyenne

Kaj: Cool, is the site is online or just internal ?

I am the author of the NT Services support for Cheyenne.

Nicolas, TryREBOL used to run on QM for the interactivity, but I've 
replaced it with my own framework now

It's still in Syllable Server configured for Cheyenne, though

And your own framework is intended to be public ?

I believe that  "modexpires" was contibuted by Will Arp

Nicolas, no, my framework is intended to stay closed, at least for 
some time

How to access to root-dir in Cheyenne ?

If you are within a Webapp, probe request/config will return virtual 
root.

But outside webapp, probe request/config will return root-dir defined 
in httpd.cfg

Your webapp definition needs to contain a 'root-dir directive.

nve, did you mean, what other external contributions have been done 
to cheyenne?

or where you looking for documentation (and the code) for the web-services 
module I did?

Yes external contributions, sorry for my english.

I know that you did web-services module, but I want to know if there 
are another external module.

I've been working on a micro MVC framework for Cheyenne.
Need to make a little documentation.
Use webapp power.

FYI: I've been doing some web sockets testing with Cheyenne. It seems 
that the specification is still a fast moving target. The browsers 
are trying to keep up, but server implementations (like Cheyenne) 
are breaking. For example, the Cheyenne web socket samples work with 
Chrome 12 on Ubuntu, but not with Chrome 14 or Safari 5.1 on Windows. 
I'm going to try the iPad tomorrow.

A good site to test web socket support in your browser is http://websocketstest.com.
It will even show the specification draft that your browser supports. 
It's different in Chrome 12 and Chrome 14.

Thanks, good info

http://www.websocket.org/is also a good site, it has good info 
about websockets.

by the way, if you use Opera Web Browser and want to test websockets, 
type opera:config to address bar, then type websocket to the search 
box and click on Enable WebSockets.

Endo, thanks for the Opera info. I did not know that and could not 
get Opera to work today.


BTW, I don't think that websocket.org is keeping up. Like Cheyenne, 
I can't get Chrome 14 or Safari 5.1 on Windows to run the Echo test. 
Does it work for you? I tried 4 Windows machines running XP and Vista.

Hmm it is strange I just tested the echo test on the http://www.websocket.org/
site when I post the message above and it was working. I test it 
with Maxthon 3 browser. But now it doesn't work with either Opera 
 nor Maxthon..

It doesn't work with Firefox, either