World: r3wp

Do they allow you to custom config?

If so, 384MB is fine. chop chop

lol, Slicehost.com: "No contracts, no setup fees."

and you can cancel at any time, if you don't like it.

This actually looks pretty good. I was leaning toward Amazon... but...

I chose Linode, because they offer a bit more for the same money. 
But it's probably a matter of taste.

If can cancel anytime, then why not try both?

well, go ahead :-) redundancy is good.

This is quite interesting, esp if we can run REBOL as the primary 
services.

Carl - how goes rebol.com redesign? Do you have any gfx proposals 
already?

Amazon is Small Instance (Default) 1.7 GB of memory, 1 EC2 Compute 
Unit (1 virtual core with 1 EC2 Compute Unit), 160 GB of local instance 
storage, 32-bit platform
If you commit to a 3 year term it is only $300 per year

maybe we should move out of this group?

P: yes, move to other group. I will respond.

$300  vs linode of $240 pa.

Forget all that.. think WEBSOCKETS!

Question: what about connect latency?

moving to ~science

Carl, I already do. You can see my site at: http://97.107.135.89/www.hmkdesign.dk/project.rsp?id=vid-ext-kit&page=info

Frankly, the biggest problem I have is long lags/dropouts on connection 
times.

Is this for altme?

or IOS?

H: cool. Cheyenne.

G: all.

My site on EC2 is private .. http://gchiu.no-ip.biz:8000/

Henrik: nice!

I'm hosting 5 virtual sites on mine using Cheyenne ...

Carl, all I can say is that I've had much fewer connection dropouts 
with my Linode than what I observe through AltME. It may not reflect 
your situation, but it just looks far more stable to me. Also you 
can specify where you want your server placed, and so have multiple 
accounts in different physical locations.

H: This AltME world runs from a different provider (via rebol.net), 
so is not typical.

Dockimbel, yep, nice and stable. Love it.

I'd be quite interested in testing R3 Chat on Cheyenne. Right now, 
it must drive the rebol.net server crazy on CGI.

(It pipes all R3 Chat connections via a CGI proxy.)

Amazon charge only for uptime .. at 8c an hour.

So, you can test for a couple of hours and then quit.  Want to run 
a windows 2003 or 2008 server to test?  Start them up and pay 12 
c an h our.

CGI proxy? They still make that stuff ;)

Much more flexible I suspect than Linode or Slicehost

but costs a little more.

T: yep. Blast from the past.

Hey, its 2010.. where's my flying car they promised back in the 60's?

Carl, you have any thoughts on websockets?

With linode you can actually do fancy multi-host redundancy stuff 
or auto reboot on some conditions, etc.  their control panel is also 
extremely well made.  you can setup your server (out a good variety 
of POSIX OSes) in a matter of minutes.

I am using both, slicehost and linode since a year now.
very good virtualisation with both of them. flash, mysql 
very stable, even a big mysql-server with only 384mb ram 
is running fine. linode has a better control panel, 
slicehost feels a little faster.

there is also another candidate for virt-hosting. 
gandi, located in france if somebody likes europe :-)
scalable via virt-shares.

https://www.gandi.net/hosting

Amazon allows you free db storage in multiple redundant locations

Speaking of threads.. Along with Websockets, HTML 5 comes with Webworkers 
(supported by Chrome as well)


Workers provide a simple means for web content to run scripts in 
background threads.  Once created, a worker can send messages to 
the spawning task by posting messages to an event handler specified 
by the creator.
The worker thread can perform tasks without interfering 
with the user interface.  In addition, they can perform I/O using 
XMLHttpRequest (although the responseXML and channel attributes are 
always null).
The Worker interface spawns real OS-level threads, 
and concurrency can cause interesting effects in your code if you 
aren't careful.

https://developer.mozilla.org/En/Using_web_workers

Here's a great webworker article / demo
http://blog.mozbox.org/post/2009/04/10/Web-Workers-in-action

that is nice!

Need to try an experiment where a worker thread sends an AJAX request 
to an RSP page, which in turns pushes back via websocket :)

Hmm, maybe Chrome 4 isn't there yet after all?

Nope, wrong again.. workers are fine in Chrome.. that last demo only 
works with FF

Here's some other demos on Resig's page  
http://ejohn.org/blog/web-workers/

Here's some code that uses flash as a websocket proxy for browsers 
that don't support websockets
http://github.com/gimite/web-socket-js

Needs some tweaking, particularly with ports.

Demo.. pushing sound to all ports

http://shinyrockets.com/echo.html