World: r3wp

I think's because the source refers to shinyrockets ...

Works for me

what works for you?

terry's demo page

When I go to it it shows Carl's picture twice with one that says 
"drag me" under it.  But when I try to drag it - it does nothing. 
 This is on IE8 and also on Chrome.

Needs Chrome 4

What exactly works for you ?  What are you doing and what happens?

I can drag image
other image turns darker when click/dragged

I do get socket closed message too

in other words it is not working for you.

Sorry, I thought the draggable picture was the demo

I don't have XP here , so I can't try chrome .. does anyone know 
when websockets are comming to other browsers? I heard some svn version 
of FF has it to and lately I heard of devel version of Webkit (I 
assume safari) also

No, that's just Jquery

What is supposed to happen is that when you drop the image, a message 
is sent to the socket and then some javascript executes to move the 
other image next to the one you drop .. something like that.

but the socket pointed to is on shinyrockets which is just a bigdaddy 
place holder page

How's the chat server demo ?

is there a chat demo? where?

doc is going to create some type of demo using web sockets

I'm upgrading my cheyenne, have to try this websockets stuffs, btw, 
nightly webkit also supports websockets (download here http://nightly.webkit.org/)

here is the only websockets demo I found online http://orbited.org/wiki/LiveHelp

here is a flash based websocket so you can support old browsers and 
use websockets now 8-)  http://github.com/gimite/web-socket-js

My demo is ready, but I found an issue to fix first with HTTP keepalive 
connections timeout colliding with web sockets timeout. The demo 
should be ready to try in a couple of hours (lunch time here).

here is jQuery websocket plugin and chat demo that I will try to 
make work with Cheyenne

Midnight here ... I'll check it out tomorrow!

great stuff Dock, btw.. 8-) I hope it can handle huge traffic!

forgot the link.. http://bloga.jp/ws/jq/wsload/s1.htm

Web sockets server-side support code is much shorter than HTTP, so, 
in theory, it should scale higher.

http://www.kegel.com/c10k.html;-P

how many connection do you estimate Uniserve can handle?

here a couple server that supports websockets http://www.tornadoweb.org/
http://orbited.org/http://www.kaazing.com/downloadmaybe there 
is something interesting for you

Don't know, that would require to create some new benchmark tools 
to test the limits. Probably 1000+ opened connections and processing 
100+ messages / sec on a 2Ghz dual core.

REBOL is too slow to hit the c10k wall anyway.

Ah, maybe not with web sockets long-lasting connections...

here is WebKit Web Socket design doc for anyone interested http://docs.google.com/View?id=dfm7gfvg_0fpjg22gh

To pass the c10k wall, we would need to replace the select( ) call 
by one of the other polling methods. That means changing the C network 
layer.

R2 may be too slow, but what about R3 and the C extension Uniserve? 
 maybe you should add a paypal button for us to start supporting 
this future development..

That would certainly boost pure static resource serving speed going 
close to Apache and in some cases, close to Lighttpd, but for the 
RSP scripts, that won't change anything. Only threading could bring 
a good speed boost there.

what is missing in R3 to have Cheyenne working on it? we should make 
sure Carl doesn't forget any feature needed, I sure wouldn't like 
being stuck with R2 because Cheyenne wont run on R3, do you have 
a list that we should relay to BrianH who will relay it to Carl ? 
I know it's still early, but having a plan should help

I mean the current version, not a feature enhanched one.. 8-)

Did looked close enough yet to have an exhaustive list, but probably 
/Library would miss the most.

When R3 features list will stabilize (beta stage), I'll make a more 
complete evaluation of the time required to port Cheyenne (lack of 
/Library can be workaround but will cost a significant amount of 
time).

Did looked => Didn't

SVN r52
FEAT: web socket realtime chat demo added.

FEAT: changed socket application's SEND function specs to SEND client 
[port!] data [string!] (/with removed).

FIX:  timeout web socket issue clashing with HTTP keepalive timeouts. 
Web socket ports are no more timed out after 15sec.

For the chat demo, after upgrading to r52, run the new Cheyenne and 
point Chrome 4 to http://localhost/chat.html.You can try opening 
several windows with different user names to see how all parts react 
in realtime.

ubercool! thank you! 8-))

Seems that the chat demo becomes the standard way to demo web sockets. 
:-)

I'll put the demo online in a few minutes, so we can use it to chat.

Btw, it's my first real try at jQuery, so the code might not follow 
the jQuery best pratices, if some jQuery/JS experts know how to make 
the code more elegant or shorter, let me know.

in the chat protocol, if a user close the browser window, will it 
signal "user quits the room" ? I should try...

Yes, it should.