One way to combat the problems of bufferbloat is for most used/of the websites to add support for SPDY. Using one TCP-connection per website instead of 6 connections per domain with domain sharding of 6 domains helps to reduce the problems. Obviously that doesn't solve P2P.
The Apache module mod_spdy is in beta, the nginx developers mentioned on Twitter they expect to have something in May.
Firefox 11 and Chrome already support it (they use the same SSL/TLS library so it was probably easier to port to Firefox than any other browser. The library was developed by Netscape at the time, I believe,). But it is disabled by default in Firefox 11 as it is the first release with SPDY. That will probably change in Firefox 12 or Firefox 13.
Having more than 50% of the browser and server marketshare support SPDY.
The recent OpenSSL stable library release 1.0.1 also supports NPN (Next Protocol Negotiation) which is also needed by those servers.
Some also do mobile phone tracking which means they look where you walk through the store, some even have software which figures out the ID of the phone. So they can combine that data with that of previous visits. Maybe they can even combine that with what you bought.
I haven't looked at NFC to see to see if that would make it easier to do that.
I would say 'killer application' applies to programmers as much as does to consumers, so 'killer platform' might be the iPhone/iPad and the language in this case might be Objective C ?
Actually, new features to be added to Flash will only be support on Google Chrome. The old plugin will still get security updates. Well, only the newer plugin-system currently only supported by Chrome. Other browsers could support the same plugin API.
1. The ability to fullscreen a video in a single step.
is already solved in Firefox and Chrome.
3. The ability to seamlessly switch between different bitrates depending on connection speed. 4. The ability to seamlessly switch between different resolutions depending on connection speed.
I don't know how seamless this is, most systems, like YouTube seem to use a simple HTTP-download methode which doesn't support that.
They use simple HTTP because real streaming through corporate proxies and firewalls sucks.
The topic of this discussion is Mozilla. And Mozilla cares about webdevelopers.
That is the reason why the choose to support Theora and later WebM, they want webdevelopers to be able to use free tools instead of proprietary and per-per-use license encumbered.
Slashdot Mirror
One way to combat the problems of bufferbloat is for most used/of the websites to add support for SPDY. Using one TCP-connection per website instead of 6 connections per domain with domain sharding of 6 domains helps to reduce the problems. Obviously that doesn't solve P2P.
The Apache module mod_spdy is in beta, the nginx developers mentioned on Twitter they expect to have something in May.
Firefox 11 and Chrome already support it (they use the same SSL/TLS library so it was probably easier to port to Firefox than any other browser. The library was developed by Netscape at the time, I believe,). But it is disabled by default in Firefox 11 as it is the first release with SPDY. That will probably change in Firefox 12 or Firefox 13.
Having more than 50% of the browser and server marketshare support SPDY.
The recent OpenSSL stable library release 1.0.1 also supports NPN (Next Protocol Negotiation) which is also needed by those servers.
I wondering what will happen if some really big solar flare takes out a lot of the electrical systems for example.
How does a cashless society deal with any natural disaster really.
And banks saving money, lots of money.
Some also do mobile phone tracking which means they look where you walk through the store, some even have software which figures out the ID of the phone. So they can combine that data with that of previous visits. Maybe they can even combine that with what you bought.
I haven't looked at NFC to see to see if that would make it easier to do that.
Sill 4 year until the next leap day :-)
Also if I'm not mistaken he is the only rapist on the Interpol list (or was it the European equivalant ?). Whatever.
It could indicate their might be an other reason he is on the list.
Atleast now he knows not to use the same private key for different purposes like last time.
I would say 'killer application' applies to programmers as much as does to consumers, so 'killer platform' might be the iPhone/iPad and the language in this case might be Objective C ?
I don't think Chromium supports H.264 either, that would be Chrome.
I would be very surprised if Debian supports h.264.
Are you sure you didn't download the codecs yourself ?
Actually last month Firefox gained market share and some reports say Chrome lost marketshare.
Although this month, for some reason, is probably an exception to the rule.
Well, Netflix already build many things in HTML5 and they would support the-video tag if it supported DRM.
They are one of the parties involved in a proposal to add DRM-support to the video-tag.
So to me it seems, they are very much willing to use it.
Actually, new features to be added to Flash will only be support on Google Chrome. The old plugin will still get security updates. Well, only the newer plugin-system currently only supported by Chrome. Other browsers could support the same plugin API.
But yes, it isn't pretty.
1. The ability to fullscreen a video in a single step.
is already solved in Firefox and Chrome.
3. The ability to seamlessly switch between different bitrates depending on connection speed.
4. The ability to seamlessly switch between different resolutions depending on connection speed.
I don't know how seamless this is, most systems, like YouTube seem to use a simple HTTP-download methode which doesn't support that.
They use simple HTTP because real streaming through corporate proxies and firewalls sucks.
Widespread use of a codec without alternatives forces people to buy a license even though the content may be free, doesn't it ?
And now Flash has been pronounced dead on mobile devices.
The topic of this discussion is Mozilla. And Mozilla cares about webdevelopers.
That is the reason why the choose to support Theora and later WebM, they want webdevelopers to be able to use free tools instead of proprietary and per-per-use license encumbered.
The consortium will always create a newer codec, it would be stupid of them not to do so.
As far as I know frameskip is an option you can turn off.
Which means no Windows XP support, nice.
Chrome/Chromium is actually build on quiet a few parts which come from Mozilla and they work together closely on that code.
"If the purpose is to advocate for all things open source"
Actually, I think the purpose is open, not open source. Open standards, that also means without royalties.
Open source is "just" the development model.
By that time Wine should support all currently running software for Windows XP ;-)
What did you expect, Skype is now a Microsoft company.
No, I don't think you can do the HW acceleration for other formats easily, probably not at all.
And HW acceleration is important, because of battery life of many devices, laptops, mobiles, tablets.