Google badmouths HTTP, proposes SPDY as a speedy successor


Recommended Posts

If you use Google Chrome you have actually been using it for ages. Most Google.com-based sites (Gmail, Search, ...) and Twitter all use SPDY automatically when using HTTPS.

To see when you're on a SPDY-powered site: use https://chrome.googl...jhmgnchggcjblin

Interesting, installed the extension to Chrome and for me Twitter and the Chrome Web Store (a Google site running over HTTPS) are both not running SPDY. GMail is though.

This is old news both Chrome and Firefox already use SPDY.

Firefox only supported it starting in v11. in v11 and v12, you have to manually enable it. it wont be enabled by default until v13.

my question is, how does one enable SPDY on their website? is this strictly limited to some Apache module right now? Can this be enabled on IIS-based sites either via IIS or some webconfig file?

What's another proprietary standard?

Contradiction in terms my friend. It's not a standard if it's proprietary, and it's not proprietary if it's a standard.

Contradiction in terms my friend. It's not a standard if it's proprietary, and it's not proprietary if it's a standard.

well not entirely true, it is, but it isn't ;)

there are several proprietary standards all ready, like Doc. which is considered a standard for a lot of things despite being proprietary.

Firefox only supported it starting in v11. in v11 and v12, you have to manually enable it. it wont be enabled by default until v13.

my question is, how does one enable SPDY on their website? is this strictly limited to some Apache module right now? Can this be enabled on IIS-based sites either via IIS or some webconfig file?

It depends on the server used, Apache needs a module, node.js has libraries for it, nginx is gaining support soon-ish, etc. And for IIS you'll probably need a proxy solution (like nginx when it's released) for quite a while.

lol I guess you didn't catch the sarcasm part about the tin foil hat.

You really need to use /s because we have no idea that you are being sarcastic as oppose to actually thinking that, we don't know that you also find it so utterly ridiculous in your head that nobody could mistake it for anything but sarcasm. It has to be REALLY stupidly over the top to get away with making a sarcastic post without /s

Will have to see if I can enable that on my web server to see if it speeds things up. :)

Whenever I read SPDY, I think of "Spidy" as in the Spider nickname.

yes! in my head i always say Spidy and not Speedy

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • You do you, I've just said that it first appeared in "home" version before it will be available in "work" one. I use Edge only because it still supports MV2 uBO extension even on Android - I'll switch when they stop.
    • I imagine that was a review or something? My reviews mostly contain a lot of images and galleries, but these are all webp too, but yeah it all adds up on the page load. Would help if you were more helpful with your critique instead of bitching and moaning like a Karen 😂 Because then we might be able to fix it for you.
    • If Valve refused to let them make the case, I wonder if they've already partnered with someone else to do it? The fact that they didn't seek permission/licence before diving straight in is incredible though
    • OpenClaw now has native mobile apps on iOS and Android by Karthik Mudaliar OpenClaw, the viral open-source personal AI agent, now has its own mobile app, available on both Android and iOS. Users can pair the app with an existing OpenClaw gateway and can start using new mobile-native features that are now available on the app. The app supports all the existing features you'd already have seen on OpenClaw's TUI, as well as some more, such as real-time and background Talk mode, action approvals, sharing from iOS, and optional access to device capabilities such as camera, screen, location, photos, contacts, calendar, and reminders. These features are available on both the Android and iOS versions of the app. What's important with these apps is that they don't run OpenClaw on your phone, but are actually just companion apps that require a running OpenClaw Gateway on an existing device, on macOS, Linux, or Windows via WSL2. To pair the app with your existing OpenClaw gateway, users need to run the command "/pair qr" on the TUI or existing chat interface, which brings up a QR code. Users can then scan this QR code to pair it up with the mobile app. There's also an option to manually pair the app by entering the host and a port. Previously, OpenClaw had been available on phones via WhatsApp, Telegram, Slack, Discord, Microsoft Teams, Matrix, and others. Now, with a native mobile app, the interface is much cleaner and more focused on just the OpenClaw, of course, with the added support for camera, screen, location, and more. It's important to note that OpenClaw comes with its own security warnings. There's always a chance of prompt injection with these tools, so users are recommended to double-check authentication, tool policy, sandboxing, and execution approvals rather than prompts alone. For users well-versed with the AI harness, a native mobile app makes it easier to approve an automation, share a link, use voice, or let an agent react to phone-side context.
  • Recent Achievements

    • First Post
      rosiecharles earned a badge
      First Post
    • Reacting Well
      Juan Dela earned a badge
      Reacting Well
    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
  • Popular Contributors

    1. 1
      +primortal
      515
    2. 2
      +Edouard
      273
    3. 3
      PsYcHoKiLLa
      143
    4. 4
      Steven P.
      100
    5. 5
      macoman
      54
  • Tell a friend

    Love Neowin? Tell a friend!