Thursday, July 16, 2009

Apache's [HTML5 Websocket] Conundrum

Setting the Context:

I think, few days back I created a enhancement request (bug) in apache bugzilla to add new Websocket feature. I got a couple of boisterous comment and I wanted to share that to the other folks. Here is more on the issue

Here is what I felt.

Death of the product is not because of the product itself but because of the people behind them, it is because of lacking foresight and shortsighted decision making. I saw death of Netscape and Fall of IE and much more. It is not because of IE is bad but because other alternatives which are too good to omit. If anything fails to catch up with competitor quickly, it means it is manhandled by those aforementioned folks. I am able to smell that in Apache. HTML5 is huge force, it can’t be omitted. I am able to play video in iPhone Safari (without Flash), Firefox 3.5, Opera (Version 10 has more than 95% HTML5 feature implemented), Webkit is in full throttle and it carries easily Safari and Google Chrome browser future forward. HTML5 also comes up with enhancement for Server. Now ball is on Server provides’/Apache’s court. So, Apache should wake up –Why? Websocket is the next driving force for the future Web platform. I don’t want to see Apache’s omission only because of Websocket support. I am able to see quite a lot of web servers are popping up. They are expecting break through – late to market is again going to be big break through for new players (server providers) who has product with those features.

I am also able to see few websocket servers. Googling will atleast give basic minimal knowledge or Answers for the questions like “why?”. I never anticipate all folks who stalk apache are Einstein but my only concern is they should not cause trouble to Apache.

I also found another comment, quite interesting. Websocket is proposed by single guy. I am not able to understand why this is matter. If million folks come up with crappy thingy doesn’t mean that – it is good. But websocket is backed by All the heavy weights – (Google, Apple, Mozilla, Opera and Microsoft (not yet sure)) So Apache’s challenge is to track these naysayers out and shift their focus on impending standards which makes them or keeps them as leader.


  1. You made the comment: "now it is IETF websocket protocol". That's wrong. Stating that it is an IETF protocol implies that there is more backing behind it than there actually is. There is a very big difference between something that is a PROPOSED DRAFT and something that is a fully supported protocol.

    I should also point out that the protocol itself is not complete. The two big blank sections in the protocol spec are indicative of that. Not to mention the frequent updates.

    Seriously, you should get your head out of your ass and actually look what's going on. Not to mention that when someone corrects you, you should really pay attention to that instead of getting defensive and putting words in peoples mouth. Yes, you did that. re-read the conversation again. And this time, it'd probably be best if you didn't hyper-focus on a non-issue/inconsequential point and understand what was/is said.

  2. Indeed; the IETF didn't invent this protocol. It was invented jointly by the WHATWG and W3C HTML working groups; the IETF merely asked for it to be submitted to the IETF because they felt it was more appropriate under the IETF umbrella than the W3C umbrella.

  3. Anonymous1:42 AM

    Thanks for sharing this article I also like website with flash designing specially the intro
    part of the website is so attractive and I agree with your view that flash presentation Increasing your web traffic and page views Add, add your website in

  4. Anonymous6:51 PM

    This comment has been removed by a blog administrator.

  5. Anonymous9:29 AM

    Dear Sir,

    I wholeheartedly agree with this post. It amuses me that there are still those who would rather stay encumbered with existing technology rather than embracing the technology of tomorrow. Simply not moving forward with web socket technology because the standards are not mature enough, is not a good enough excuse. As we saw, Microsoft destroyed Netscape by adding more robust features which later on became standards themselves. A good example of this is the XMLHttpRequest object (without which Ajax would not be possible). I'm tired of depending on long Ajax polling (waste of resources, adds application complexity) - bring on web sockets!


  6. Anonymous6:52 AM

    Here here! +1


Thanks for reading and welcome for commenting...