World: r3wp

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.

Chrome is probably aggresively caching

You should put some no-cache directives on that page ...

I always get redirected to http://70.68.163.178/ws2.html

Nothing comes up for me in FF 3 or Chrome 4 at http://www.ddmind.com:81/moon88

well, I see a little red square top right

Works here with Chrome 4.

Seems to work here too.

I am using 0.9.19, no problem just wanted to mention. 


@Graham: can I ask why are you doing this (checking for file OR data 
in request/content): 
either file? filedata/2 [ 

 write/binary join get-user-dir filename read/binary join incomingdir 
 filedata/2
] [ 
	if filedata/2 [
		write/binary join savedir filename filedata/2
	]
]


I imagine if file is bigger it get's saved and you copy it. But how 
can you then determine the incoming/pwd is this some cheyenne default?

cause there is a default directory for all incoming file data ...

Ok.. Chrome has a "prefetch dns" option..  so my demo was caching 
the ip rather than the domain

I've updated the domain to a proper dns record, rather than just 
forwarding.

If you still can't see the demo, turn off "prefetch dns".. temporarily

http://shinyrockets.com/ws2.html

Article regarding chrome dns prefetching

http://tinyurl.com/4adsdd

This is helpful as well.. in the chrome address bar type;
about:dns

Methinks the Cheyenne world would be much better serviced using Cheyenne 
chat rather than this archaic, uneditable, uncustomizable, proprietary 
and  difficult to enter thing called Altme

All good criticisms, except the "proprietary" one. It could be worse 
though - it could be a web chat.

Yeah, web chats....  avatars, skins, website integration, API integration 
with gmail, animations, sound, video and other media integration... 
those things really suck

Yup, I agree, at least the parts that need the web to do (which isn't 
much on that list).