World: r3wp

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

<?php
$contact = array("name" => "Ben");
$contact_encoded = json_encode($contact);
header('Content-type: text/html');
echo $_GET['callback'] . "(" . $contact_encoded . ")";
?>

Anyone know the rebol equivalent to the above code?

And would it work in cheyenne?

I most interested in the call back line to send json encoded data...i 
can't get a jquery script to accept anything I send back

If you want to send JSON, you'd better set an apropriate MIME media 
type with e.g.

<% response/set-header 'Content-Type "application/json" %>


Cheyenne has no JSON converter, but you'll find something at http://www.ross-gill.com/page/JSON_and_REBOL
.

And maybe it's a good idea to try to serve some static JSON data 
first instead of generated data to narrow down where the problems 
are.

Christian, The data in eh browser looks right now...thanks, but teh 
jquery script is still not working. I believe it has to do with the 
callback or lack there of ...

that seems to be returning javascript (ie. a call to a JS function), 
rather than JSON...

(Which some people call JSONP.)

The javascript is looking for the data in a callback...how do I wrap 
the data in a callback using rebol and cheyenne?

just return the Javascript call, like the PHP does above.

ie. if the function is called "myFunction", just return "myFunction({myData: 
1, ...})"

Thanks for the response Gabriele, but I just can't get this to work.
If i'm using an rsp page to send back the request:
I've got this:
<%
data: {
one
: "Singular sensation",
two
: "Beady little eyes",
three
: "Little birds pitch by my doorstep"
}
response/set-header 'Content-Type "application/json"
print rejoin ["myfunc" "({" data "})"]
%>

Does not work...

response in web page includes the function name which does not look 
like json data typically served back

This works for me

	response/buffer: copy data
	response/set-header 'Content-type "application/json"

Graham! You are the best...thanks again!


I had to use echo mode on the client (and i'm not really sure what 
that means) but it works!

Glad it works ...

More correctly Nenad is the best ...

Can Cheyenne do SSL?

Not standalone, you would need a SSL front-end for that, like stunnel 
or nginx.

Cheyenne-server.org is taking a long while to serve the wiki pages.

Main PHP process froze. I'm restarting it.

Done.

btw: I added few lines to cheyenne so it solves my only major hurdle 
with javascript (I need to write a lot of javascript for my apps, 
and I use sort of functional style). shorter syntax for anonymouse 
functions + returns. Nothing big or complex...
f{ a, b | .... }  ==>  function ( a, b ) { ..... } 
r{ a, b | a + b } ==> function ( a, b ) { return a + b } 

not sure if it's usefull to anyone else or has place in real cheyenne, 
since it's just more of a hack (and not standard in any way). If 
anyone need it, let me know)

I just added few lines to parse where it compiles in it's multilang 
stuff - which is btw very good since it does it only once and then 
holds cached version same as for languages :)

nenad designed cheyenne very well, that's why it's so fast!

Here's inspiration for Cheyenne/Red:

http://gwan.ch/

I am not sure that web developers are ready to jump to C for writing 
their server-side scripts (especially with error reports that include 
CPU registers content :-) ).

The main benchmark graph is basically testing how fast each server 
is able to copy chunks of memory. ;-)
http://gwan.ch/benchmark

Also, this is closed source software.

I tried gwan on Windows with a logs directory as described in the 
manual. It crashed.
Also the listen options on startup did not work.

Copying chunks of memory is what you do when serving static files, 
isn't it?

Cheyenne/Red doesn't have to be closed source and write scripts in 
C

Yes, especially when you're serving only to localhost (like in the 
gwan benchmark).

The main point is that G-WAN basically uses the BeOS/Syllable architecture: 
one process with worker threads

That's what I plan to do too for Red.

Specifically, it uses a pool of one thread per core for an event 
based architecture

That's the only rational way to use threads IMO too.

Well, there you have it: the other web servers don't

Sqlab, G-WAN for Windows is discontinued, a year ago or so

Yes, but I just used the examples as they are explained in the manual 
for the windows version.

It seems to have been developed on Server 2003. Maybe it doesn't 
work on newer Windows versions. It was discontinued in September 
2009

That was probably when G-WAN had been in development for a year, 
so in any case it would be incomparable to the current Linux version, 
which is not mature yet, either

Just one question, nothing urgent. Would it be possible or smart 
if cheyenne would return http 401 to ajax request when the session 
times out? Now it basically return 200 and login form html (so I 
have to test for presence of </form>) instead of usuall JSON.