World: r3wp

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).

don't forget unintended deletion of forum channels!

... CSS, database access, acting as a proxy to servers, JQuery, Google 
map integration, Amazon S3, OpenID, AtomAPI and other RSS integration, 
Delicious... man, i HATE that stuff.

... integrating Processing... 
http://processingjs.org/exhibition

And hacking of php ... yep

Web chat it will be

I have a hotkey javascript library I'll hook up.

and some sound js lib as well

I'd ask Terry to write it for Cheyenne... but I suspect that we'll 
never be able to reach it because of dns issues!

It's funny, Terry, but I keep agreeing with your sarcastic list once 
I filter out the stuff that I can do easier without a web browser, 
or that aren't necessary at all when you aren't using one.

I like some of the stuff on that list, but I like doing it better 
without HTML/JS/CSS.

Must be just me, I guess.,

Server-side web stuff is fun though.

Brian, I'm comparing with Altme only.. Desktop vs client/server is 
a whole other argument.

Graham, did you shut off the Chrome dns prefetching?

Terry .. I gave up

Hmm, maybe programming isn't your forte.

You don't say that to your patients as well, i hope ;)

Turning off DNS prefetching is explained here : http://jackkonblog.blogspot.com/2009/03/turn-off-dns-pre-fetching-in-google.html

Chrome has a great JS debugging tool.. In the icon on the top left 
that looks like a page, open developer -> Javascript console

Add this to the $(document).ready(function(){  ... } in chat to submit 
chats using the enter key;

			$("input").keypress(function (e) {
				if (e.which == 13 ) {
					   ws.send('m' + user + ': ' + $("[name=post]").val());
					   $("[name=post]").val('');
					   $("[name=post]").focus();
				}
			});

Updated version of Doc's chat example.. 
- Enter key support for login and posting chats
- Cookie mgmt for user name
- various "tweaks" to the JQuery 

chat2.html:  http://pastebin.com/m66a38d50

Thanks Terry, I've upgraded the chat demo with most of your changes. 
I've also included an alert message for non-compliant web browsers.

Need to fix the 'signout' updates to other ports.. it's not sending 
the "bob leaves" message, and it's not updating the user list <div>

No cookies? I like cookies.

I've opened 2 Chrome windows logged in the online chat demo from 
both of them and I receive correctly in the first window the quit 
message from the second one. How can I reproduce your issue?

Cookies: well, it would be a nice addition to a real chat app, but 
the point in this demo is to show web socket usage, not to build 
a full-featured chat app. If you want to build a full chat app, you're 
free to take my demo code and extend it as far as you wish.

Btw, you may need to Shift+Reload in Chrome to get the latest chat 
code.

Shift + Reload (I am used to it) = F5 btw ....

I'm not sure for Chrome, isn't F5 a simple page reload (without clearing 
the cache)?

Ahh.. shift-reload to clear cache, and nice debugging/developer tools.. 
Chrome is well thought out.

Doc, i was referring to my modified chat.html regarding the 'signout' 
issue.

Does Chrome have anything like FireBug or WebDeveloper extension 
in FF?