Why are you bothering about HTTP servers if we are talking about WebSockets
and _NOT_ HTTP? :)
I think WebSockets are almost necessary for the future of the web. I've been
developing some addons for Firefox in the past months, and wanted to put an
XMPP/Jabber chat client/UI (some kind of server-client interaction based on
XMPP) in my extension to let users communicate faster and be everytime
updated on what's going on. I tried to use HTTP binding but it was a
disaster! Too many headers, overhead and slow transfers! My Apache 2.2 was
melting with just 2000 users (just working as a proxy)! I have a single
server, not a cluster nor a load balancer. I had to relay on XMPP4Moz (an
extension built upon Gecko XPCOM APIs) and I used a socket. -problem
(almost) solved-
It really helped a lot! Also with my super-slow-UMTS-usb-dongle (thank you
H3G -.-'' )!
I would really like to see Facebook, Google and also my own servers being
using websockets (J2EE, ever heard of it? PHP/CGI is not THE solution).
So why not spreading this technology with some $.ws("url",{/*stuff*/}); ?
Even if it works only on chrome, bringing such a great improvement to jQuery
could force the web developers and web browsers to move forward (also if
just a bit)!
jQuery is not just a toolbox, it is becoming some kind of "standard"! Let's
move it forward to force others to follow it! :)
Is it science-fiction for you? I hope not...2010/1/20 DBJDBJ <dbj...@gmail.com> > 1. > Are WebSockets officially part of HTML5 ? Mike I can see the specs, > yes. But this is definitely would be the most questionable HTML5 > detail, it seems to me? > This almost introduces synhcronous two-way sockets in the middle of > totaly async www infrastructure... There is no amount of fibre today, > which would be enough for all www users to connect to www with a > single WebSocket from their browsers. That much is obvious. WebSockets > require additional server-side configuration and setup which (for > example) Appache (out of the box) does not support today. Neither does > IIS, it that matters. > 2. > On each and every WebSockets spec, I see no other author of the spec > but Ian Hickson, Google Inc. Which strikes me as odd? Is he (and > Google Inc) such a capable and unqestionable WebSockets, www leader ? > 3. > This very simple question is a very big question for WebSockets > future : Who and where and why, will provide full WebSockets > functionality on the server side ? > ( Google will because of CHROME OS ). > > --DBJ > > -- > You received this message because you are subscribed to the Google Groups > "jQuery Development" group. > To post to this group, send email to jquery-...@googlegroups.com. > To unsubscribe from this group, send email to > jquery-dev+unsubscr...@googlegroups.com<jquery-dev%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/jquery-dev?hl=en. > > > > -- Marco Pivetta - Ocramius Aethril Standard Ogame Project - StOgame http://www.stogame.net Making Ogame a better place... Sent from Padova, Veneto, Italia--
You received this message because you are subscribed to the Google Groups "jQuery Development" group.
To post to this group, send email to jquery-...@googlegroups.com.
To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en.
