Opera Desktop Team blog header

Opera Labs with SPDY released

,

An interesting new technology appeared out of Opera Labs a few minutes ago: a build with the low-latency HTTP pipelining replacement SPDY. In short, it means faster and prioritized connections between the browser and supporting server.

Head over to the Opera Labs blog to read all about the protocol and grab the downloads while they’re still fresh.

The feedback we are interested in for this release is whether you have any performance or consistent connection issues. Please use the comment section in the Opera Labs blog post.

SPDY has already been deployed on many Google services and on Twitter. The blog post includes some information about how to make your web site SPDY ready so you can take advantage of the new performance potential.

WARNING: This is an Opera Labs build: It contains work in progress, which may also have severe known issues, including crashes, and data loss situations. In fact, it may not work at all. Opera Labs builds are not based on current Opera Next releases.

More fixes for Opera 12First bite of 12.50 ‘Marlin’: Clipboard API, redesigned key event handling, -webkit- CSS, and Notification Center

Comments

kapsi Friday, July 6, 2012 10:36:06 AM

Nice. I hope it won't take a year to get it in stable Opera.

SaveTheCatsICEsavethecatsice1 Friday, July 6, 2012 10:37:31 AM

Cool!

earth01 Friday, July 6, 2012 10:38:37 AM

up

What about WebSockets too ? Are the standard specifications finished ?
Is there some news about its support in Opera ?

Hiramapriorimeister Friday, July 6, 2012 10:51:40 AM

Originally posted by earth01:

up

What about WebSockets too ? Are the standard specifications finished ?
Is there some news about its support in Opera ?

http://www.opera.com/docs/specs/presto2.11/ (Presto/2.11.337)

earth01 Friday, July 6, 2012 10:56:42 AM

Originally posted by apriorimeister:

http://www.opera.com/docs/specs/presto2.11/ (Presto/2.11.337)


Ok, probably in the next version with some chance.

Satan D. Lucifersupertrol Friday, July 6, 2012 11:02:08 AM

Question:

Does it contain the fixes in Next 12.01 build 1491? or completely separate build?

bachokocho Friday, July 6, 2012 11:16:40 AM

I don't know, but its version number is 12.01 1495 smile already tried it, and I'm tempted by the idea to install it over my Next 1491 smile

Agoagostinog Friday, July 6, 2012 11:47:03 AM

Nice addiction!!!

ohyeahgod Friday, July 6, 2012 2:08:18 PM

Cool!!

kapsi Friday, July 6, 2012 2:32:23 PM

Originally posted by agostinog:

Nice addiction!!!


Aren't we all addicted...

CryioAcryion Friday, July 6, 2012 5:02:06 PM

Originally posted by supertrol:

Question:

Does it contain the fixes in Next 12.01 build 1491? or completely separate build?

Build number for Opera Labs doesn't matter. I quoted Ruari bigsmile

Rafael Luikrafaelluik Friday, July 6, 2012 5:34:14 PM

Do you want my feedback?? Don't implement things that aren't in web standards projects which are open to all parties to contribute Opera! down down down down down down

Kajetan Świtalskikswitalski Friday, July 6, 2012 5:39:23 PM

Originally posted by supertrol:

Question:

Does it contain the fixes in Next 12.01 build 1491? or completely separate build?

Yes, it contains all those fixes that are in build 1491.

turtlepro Friday, July 6, 2012 9:02:26 PM

Okay! I reactivate my Windows XP. But, why not! Mankind is in the beginning of computing and will this things have till I don't not what. Spare resources is a wisdom we have to understand. rolleyes

NEOAethyr Friday, July 6, 2012 11:20:33 PM

When the time comes will there be a way of disabling it?
I don't trust the current protocol, let alone a new one.
This also makes more work for me in the long run...

And I don't quite agree with all the points being made over this spydy protocol.
Why in the world would you compress the headers anyways...

Why not just force support of compression in the headers, and hopefully when more servers support such things then well...

Ex. Accept-Encoding:
x-deflate,deflate,x-gzip,gzip,x-compress,compress
Just a bs example, I just saying, why not just enforce it a little by telling the server you support this or that compression standered.
It's up to the servers themselves to support it.

I think this is just a bad idea and a waste of time...
Sorry, just to put the point across, please make a way of getting rid of it too if you keep it...
I don't wanna have to impliment that crap in my software... sorry.

DillonAstrophizz Saturday, July 7, 2012 3:00:08 AM

What don't you trust about the current protocol (or spdy)? And what's wrong with requiring compressed headers?

Alwyn van DeventerFunkyMunky1723 Monday, July 9, 2012 9:07:20 AM

It's definitely nippier than my Opera Next installation. In fact, I've been trying out Opera for quite some time now, but always ended up using Firefox as Opera just didn't do it for me.

This release seems to do the trick, at least in terms of speed.

GTSSGela2010 Monday, July 9, 2012 11:04:23 AM

very good version. long ago such wasn't

cunjing Monday, July 9, 2012 11:17:16 AM

Thank you for good job!
This version is so fast!
I am looking forward to released SPDY version.

GTSSGela2010 Monday, July 9, 2012 11:29:25 AM

Originally posted by cunjing:

Thank you for good job!
This version is so fast!
I am looking forward to released SPDY version.

12.01.1495 works very reliably, not only the speed

Kajetan Świtalskikswitalski Monday, July 9, 2012 1:46:01 PM

Originally posted by NEOAethyr:

When the time comes will there be a way of disabling it?


Yes, in the Labs build there is already a way of disabling support for SPDY (opera:config -> Use SPdy2/Use SPdy3) - we're going to keep it.

Karl Dubostkarlcow Monday, July 9, 2012 2:06:11 PM

Originally posted by rafaelluik:

Don't implement things that aren't in web standards projects which are open to all parties to contribute Opera!



SPDY is being discussed currently by the HTTP WG. You can participate to the discussions if you are yourself experimenting with it. It is valuable input for implementers community to have real implementations of flavors of SPDY to be able to give input to the HTTP/2.0 which will have ideas and patterns of SPDY. Note also that when people say "SPDY implemented" it is usual a partial implementation of some of the features of SPDY. The discussions on HTTP WG mailing list are interesting. http://lists.w3.org/Archives/Public/ietf-http-wg/

Karl Dubostkarlcow Monday, July 9, 2012 2:07:45 PM

Originally posted by Astrophizz:

What don't you trust about the current protocol (or spdy)? And what's wrong with requiring compressed headers?



It might be useful for people to be able to test Web sites and/or client implementations in a context where SPDY is not used. So it is practical to be able to deactivate it at will.

Rafael Luikrafaelluik Sunday, July 22, 2012 2:32:58 PM

Originally posted by karlcow:

Originally posted by rafaelluik:

Don't implement things that aren't in web standards projects which are open to all parties to contribute Opera!

SPDY is being discussed currently by the HTTP WG. You can participate to the discussions if you are yourself experimenting with it. It is valuable input for implementers community to have real implementations of flavors of SPDY to be able to give input to the HTTP/2.0 which will have ideas and patterns of SPDY. Note also that when people say "SPDY implemented" it is usual a partial implementation of some of the features of SPDY. The discussions on HTTP WG mailing list are interesting. http://lists.w3.org/Archives/Public/ietf-http-wg/

Many thanks for your reply and information. smile

Fitrifitrisartika Saturday, August 4, 2012 12:54:25 PM

heart yes

yop plavideobuzz Monday, September 3, 2012 11:33:40 AM

nice, it could be usefull

Write a comment

New comments have been disabled for this post.