World: r3wp

No, the bindind between the URL (/chat.rsp) and the web socket app 
(chat) is done in the httpd.cfg file with the 'socket-app keyword.

Got the chat demo running online. If you have a web socket enabled 
browser (ex: Chrome 4), go visit here : http://demo.cheyenne-server.org:8080/chat.html

damn, this is small stuff.

Posting here the link for the server side of chat app : http://code.google.com/p/cheyenne-server/source/browse/trunk/Cheyenne/www/ws-apps/chat.r

Hope this will inspire some of you to ride the new wave of realtime 
web application that will surely start to come this year.

Be back later.

this web chat is using websocket on chrome (and comet in other browser).
http://www.ddmind.com/modules.php?name=gdp_easy_chat

It's a Rebol server and It works pretty well...great uptime and low 
cpu use.

what server is that GDP-Server Alpha (Win32) REBOL ??

here is a quick overview of the rebcomet server:

http://www.screencast.com/users/Perekk/folders/Jing/media/6465c6f2-3c5c-4237-9ce4-0e6d61f74fb1
and 

http://www.screencast.com/users/Perekk/folders/Jing/media/d5c252ef-29dc-4c49-ac10-2ce98cd4518a

it's a server that I'm using in some commercial project, currently 
in alpha stage

is it open source?

I will open source it (and documenting it), when it come out the 
alpha stage.

Currently the dialect is changing every day, so now would be too 
confusing

I would like to replace the tcp http server  with cheyenne.

Now I'm using a modified hipe server by Maarten Koopmans, but it's 
not async, so some things are currently not possible

definitely, use cheyenne ;-)

cheyenne is not only a great server, it's code is pure art, you can 
make it do whatever 8-)

I wrote an article about the new framework on our Syllable sites:

http://web.syllable.org/pages/index.html#id-2010-01-02-22-16

this is a start of  a sample app using extjs lib http://www.ddmind.com:81/moon88

As Doc said I think that 2010 will be the year of these kind of applications

Yes Will, I'll try to dive into the code asap :-)

In addition to being the Year of the Linux Desktop, of course ;-)

(will be the year of duke nukem forever too)

Wow, that server of yours is awesome

My article is on OSNews now:

http://www.osnews.com/story/22681/Syllable_Web_Server_Cheyenne_Gets_WebSocket_Framework

Kaj: thanks very much for the article!

Davide: nice work, I'm sure that Cheyenne would make a good front-end 
for your framework.

thanks kaj, thanks doc. 
Anyway it's great to see cheyenne on osnews.

Now that there's a framework inside the main Cheyenne process, I'm 
considering adding more UniServe based implemented protocols to Cheyenne, 
like HTTP, POP3, IMAP and MySQL. There are of course all async.

HTTP is the most advanced, I use it in several apps in production. 
POP3 is beta. IMAP has just a few lines of code. MySQL is alpha, 
but working.

For web socket apps, the advantage would be to not have to require 
'do-task to use the sync version of these protocols from a worker 
process. OTOH, that would put more burden on the main process lowering 
its scalability. So I've not decided yet, this would probably require 
good benchmarking first.

Would you still need your own protocols with R3?

Maybe not if there are already there.

I updated the article on the Syllable sites with the online chat 
demo

I had hoped it would be in time for OSNews, but I thought I had better 
make use of the current slow news period. I'm not sure they would 
report on just some web server

It occurred to me that no contact information is published anywhere 
for Cheyenne, so I linked this chat from the community links on the 
Syllable sites

I'll add contact info in the chat demo.

anyone here had problem using mod-alias? I'm not using it but have 
an old patch and would appreciate some user cases where current version 
fail before subitting to Dock, thx

I found this example of doing the file upload in cheyenne but I don't 
understand it fully. http://rebol.wik.is/Cheyenne/Upload-file.rsp

where does the 'infile come from?

aha, I see it now..


btw: I noticed one thing.. when I uploaded file request/conetnt keys 
returned to strings from words .. so I had to do req: request/content 
forskip req 2 [ change req to-word first req ]  to fix them back

What version are you using? I remember fixing such issue a few month 
ago.

It has been fixed in the SVN repository but the bug is present in 
v0.9.19.

If you want to fix it in 0.9.19, here's the patch :

RSP.r => decode-multipart function => line: insert tail list name
should be : insert tail list to word! name

You can also copy/paste the latest 'decode-multipart function in 
your 0.9.19 RSP.r file, modifications are minor and not dependent 
on other parts.

Janko, if you want to write some additional documentation for my 
example, I can add it ...

Your wiki looks really nice.

Just using the defaults with absolutely no customizations!

When I posted that link to my demo, I had only just updated the nameservers 
for shinyrockets.com.. should have propogated everywhere by now
http://shinyrockets.com/ws2.html

Nope.

There's no www.