3 ms·
I wish there were more tools for Firefox 11 and SPDY, absolutely no way to tell what is going on. But I guess the beta and SPDY support is far too young for no
by ck2 15y ago
I wish there were more tools for Firefox 11 and SPDY, absolutely no way to tell what is going on.
But I guess the beta and SPDY support is far too young for now.
The only indicator I have is the response headers will add
X-Firefox-Spdy: 1
...which I see on Google services and now twitter.
I guess someone could write an extension to watch the response headers and show an indicator.
- chengsun 15y agoHere's a version for Firefox: https://github.com/chengsun/moz-spdy-indicator https://github.com/chengsun/moz-spdy-indicator
- ck2 15y agoImpressive, many thanks - I was reading up on how to use visitResponseHeaders but you saved me a bunch of time. Is that you in the top three Google Code-in 2011 Grand Prize Winners? I guess we can look forward to great things from you over the years.
- chengsun 15y agoYep, that was me :) I worked on better integration of VLC plugin in browsers on Linux; that was a lot of fun.
- cpeterso 15y agoThanks! I guess I can now rm -rf moz-spdy-indicator my work-in-progress. :)
- cpeterso 15y agochengsun: in indicator.js, what is the lifetime of SPDYObserver.cache? SPDYObserver.observer() saves every URL in the cache, but never flushes old URLs from the cache.
- chengsun 15y agoI was concerned about that as well. I just rewrote the observer to store data with the tab instead of in the cache indefinitely.