Instant messenger like systems help illustrate the
problem:  Try http://www.meebo.com/ or the integrated
Talk/Chat feature of GMail for examples.  Long-running
requests solve a class of low-latency communication
techniques that would otherwise overwhelm the server
with polling traffic for similar performance.

The Meebo folks claimed they tried their hand at
fastcgi and gave up to create their own custom
lighttpd plugin.  I'd love to see what Armageddon has
in mind to solve this.  

Cheers,

-San

--- Richard Friend <[EMAIL PROTECTED]> wrote:

> One of the primary reasons for the success of the
> http protocol and the
> Internet in general its stateless nature, this is
> being further extended
> into things like REST web services.
> 
> In a model like this wouldn't you have to ensure
> that everything is thread
> safe?
> 
> To me this looks like a step backwards, although
> maybe I am just not getting
> it.
> 
> On 4/22/06, Jon Tirsen <[EMAIL PROTECTED]> wrote:
> >
> > But that's just on the browser side of things
> which is relatively easy
> > to do (although you can't use XHR of course). The
> hard thing is
> > scaling things on the server side because of the
> > one-fastcgi-process-per-request problem and the
> fact that a "Comet
> > request" never ends.
> >
> > On 4/22/06, Andrew Kaspick <[EMAIL PROTECTED]>
> wrote:
> > > I see no point in holding back either.
> > >
> > > I was at CoR as well and saw the same stuff.  I
> thought it was cool,
> > > but it's not as groundbreaking as you might
> think.
> > >
> > > Comet uses iframe hacks and armageddon uses a
> flash "hack".  Yes, I
> > > said hack. :)  Although the solution looks much
> cleaner, I don't
> > > believe it to be as portable a solution because
> of the use of flash,
> > > but does that matter???  I don't know, we'll see
> I guess.
> > >
> > > Looking forward to seeing more info on
> Armageddon though.
> > >
> > > On 4/21/06, Eric Woodward <[EMAIL PROTECTED]>
> wrote:
> > > >
> > > > That's lame. Please ruin the "surprise".
> > > >
> > > > --ejw
> > > >
> > > > Eric Woodward
> > > > Email: [EMAIL PROTECTED]
> > > >
> > > >
> > > > On 20-Apr-06, at 6:27 PM, Giles Bowkett wrote:
> > > > >> Are we rewriting a complete messaging
> infrastructure software in
> > > > >> Rails
> > > > >> here or is there a way of doing this that's
> so incredibly clever
> > and
> > > > >> simple that I've completely missed it.
> > > > >
> > > > > There is a way of doing this that is so
> incredibly clever and simple
> > > > > that you've completely missed it.
> > > > >
> > > > > I got to see it at Canada on Rails and I
> think you'll see it soon
> > > > > enough. I'd tell you but I don't want to
> ruin the surprise.
> > > > >
> > > > > --
> > > > > Giles Bowkett
> > > > > http://www.gilesgoatboy.org
> > > > >
> _______________________________________________
> > > > > Rails-core mailing list
> > > > > Rails-core@lists.rubyonrails.org
> > > > >
>
http://lists.rubyonrails.org/mailman/listinfo/rails-core
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> _______________________________________________
> > > > Rails-core mailing list
> > > > Rails-core@lists.rubyonrails.org
> > > >
>
http://lists.rubyonrails.org/mailman/listinfo/rails-core
> > > >
> > > _______________________________________________
> > > Rails-core mailing list
> > > Rails-core@lists.rubyonrails.org
> > >
>
http://lists.rubyonrails.org/mailman/listinfo/rails-core
> > >
> > _______________________________________________
> > Rails-core mailing list
> > Rails-core@lists.rubyonrails.org
> >
>
http://lists.rubyonrails.org/mailman/listinfo/rails-cor
> >
> > _______________________________________________
> Rails-core mailing list
> Rails-core@lists.rubyonrails.org
>
http://lists.rubyonrails.org/mailman/listinfo/rails-core
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to