World: r3wp

SVN r51
FEAT: /ws-apps folders are now protected from direct access.

FEAT: modified socket apps source files are reloaded and used by 
new clients.

FIX:  web socket application's 'session object renamed to the more 
accurate 'rsp-session.
FIX:  'do-task calls now supported in 'on-timer handler.
FIX:  scheduler issue with deleted jobs.

Moving right along :)

ooh.. the diagram is looking shiny

Part of the confusing bit is the ws.html connects to the ws.rsp script 
first.. I would have thought of it as on the front end.

I agree that's a bit confusing.

how does /on-done work?

That comes from the way web socket's connection are initiated, it 
starts like a simple HTTP GET request and the server is supposed 
to validate that request, check access authorization if required, 
etc... So, to avoid duplicating work, I choose to re-use RSP framework 
as much as possible. The initial ws:// URL must point to a valid 
RSP script so that the server can check, for example, RSP session 
cookie for access rights.

So, during the connection time, the target RSP script is not executed 
(unless you pass it a 'do-task in the 'on-connect handler). This 
target RSP gets associates with the opened socket until it's closed.

/on-done installs a callback handler (block! or function!) that gets 
invoked when the job sent by 'do-task to the RSP script is finished.

How do you pass a do-task to an rsp script? (what variables are passed?)

must it be the initial rsp script?

do-task takes a string! argument. You can pass anything you want 
using that value.

I put that "do %test.r"   in the timer without using do-task.. and 
it worked fine.. i guess that was blocking though?

You can also use the 'rsp-session object to permanently share values 
with the RSP process (to be usage carefully, see %ws-test-app.r).

I've fixed several issues with timers, so yes probably. I still don't 
get why you want to "do" a script on each event...

to be usage => to be used

i was just experimenting.

(as far as putting the "do" in the timer)

As for "do"ing a script with each event, I suppose the traditional 
way would be put all your code in the ws.app.r ... do ing was more 
like "include"

The last revision will auto-load your socket app if you've modified 
it, but only new incoming connections will use it. Established connection 
will still use the older version. Once every client disconnects from 
the old version, the old app version is dropped out.

Ok.. i'm officially digging Cheyenne's websockets

some examples coming down the pipe

Here's a modified on-message from ws-test-app.r 

	on-message: func [client data][						
		;send data
					
		do-task/on-done data func [client data][	 
		

   ;data: do/args %/c/cheyenne/cheyenne/test.r {one "two three"}		  
       ;doing a script passing /args

   data: read http://www.php.net/usage.php				      ;as 
   a proxy to PHP server
			
			send/with data client
		]
	]

and the test.r script... (drop in Cheyenne's root)

rebol []
 
x: to-block system/script/args
 
to-string x/test

opps, change last line of test.r to 

to-string x/one

Here's a little demo that allows you to drag an image, and once you 
stop dragging, sends it's position to a .r script via a socket. The 
script then sends a message to another image on the page to reset 
it's top and left position to match the dragged image, +100 px

The updated ws2.html page

http://pastebin.com/m4f61ffd7

the updated ws-test-app.r 

http://pastebin.com/m7c39d7c6

and the test.r script is (place in the Chyenne root)

rebol []
 
x: to-block system/script/args
 
left: x/left + 100 
top: x/top + 100

left: join left "px"
top: join top "px" 
 

data: rejoin [{$('#carl2').css("top", "} top {");} {$('#carl2').css("left", 
"} left {");}]

Demo

http://shinyrockets.com/ws2.html

Sorry Terry.  The shinyrockets link leads to a godaddy parked page 
from here.

cached

Added an "easing" effect to demo

Alternate upgrade method .. download binary patch, read the current 
version, xor it, write it out as the new version .. and then the 
same as in your script above.

Terry's demo http://70.68.163.178/ws2.html

Doesn't work for me .. when I reach that page, it says "socket closed"
Dragging the image doesn't do anything.

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