Really how many Javascript security holes have their been the last 10 years ?
In 99 of the 100 cases it was the Java or Acrobat Reader plugin which was the real problem. They just use Javascript to deliver it, but didn't have to.
What they usually do is create one CSS-file with all the smaller images included. The CSS-file can be cached, but still saves a whole bunch of requests for small images.
Unless Opus becomes a IETF and W3 standard with "Mandatory To Implement" status for any browser that wants to claim support for any of the standards involved.
If it gets that before any new codec comes to town, then the bridge will already be burned.
It could be a problem with Firefox hardware acceleration and your graphics card/driver.
At the end of the about:support page there is a 'Graphics'-heading which tells you what you have and if it is enabled.
To enable or disable hardware acceleration: - to check or uncheck the box: Options -> Advanced -> General-tab: Use hardware acceleration when available
This is exactly why under the latest rules no rides in the peloton can have any injections what so ever. Obviously unless done so by a physician when there is a known problem.
Actually, this was on the first page of the article:
[ Move over, Amazon -- IaaS providers are elbowing into the cloud. [0] See how they compare in InfoWorld's slideshow. | Get the no-nonsense explanations and advice you need to take real advantage of cloud computing in the InfoWorld editors' "Cloud computing in 2012" PDF special report. [1] | Stay up on the cloud with InfoWorld's Cloud Computing Report newsletter. [2] ]
Basically every program currently uses compositing (sometimes the toolkit/libraries does it for the program) or can easily do so.
Compositing seems to be the most efficient way to do it, but compositing was something that was added later to X as an extension.
They want to get rid of everything else in X and just use compositing as everything else can already be handled by the Linux kernel (this means wayland won't work for Unix as I understand it).
X just has a whole lot of legacy code and some overhead.
The reason why it is possible to build Wayland (replacing X is really big task) is because Wayland just does this small thing, compositing and all the other stuff can be handled by other parts of the system because in the years support for that has been added to the kernel or toolkit-libraries and so on.
The reason why Wayland does not do networking... is because again, other systems can handle that. RDP, X11, SPICE and even VNC.
Slashdot Mirror
Yes, I know that. I'm just saying it is a much smaller problem than the plugins.
Especially with rapid release like Chrome and Firefox use to keep your browser up to date.
Really how many Javascript security holes have their been the last 10 years ?
In 99 of the 100 cases it was the Java or Acrobat Reader plugin which was the real problem. They just use Javascript to deliver it, but didn't have to.
You are probably saver just disabling plugins like Java, Acrobat Reader and maybe Flash (or at least use the lastest version).
The Javascript is almost never the vulnerable part, it just used by many bootstrap it. But they don't have to do that.
No worries, IE still supports MHTML which doesn't have the lenght limit.
Many do both, include the sprite (as such a grid is called) in a CSS-file, the CSS-file is referenced on many pages on the site.
The biggest problem with TCP is False Start, but which means many small HTTP-requests will still be a lot slower than sending one large HTTP response.
What they usually do is create one CSS-file with all the smaller images included. The CSS-file can be cached, but still saves a whole bunch of requests for small images.
Ads are always loaded from other domains, don't worry about that.
Unless Opus becomes a IETF and W3 standard with "Mandatory To Implement" status for any browser that wants to claim support for any of the standards involved.
If it gets that before any new codec comes to town, then the bridge will already be burned.
Some Windows graphics systems are also blacklisted, actually the graphics performance on my Linux machine is better than my Windows machine.
It could be a problem with Firefox hardware acceleration and your graphics card/driver.
At the end of the about:support page there is a 'Graphics'-heading which tells you what you have and if it is enabled.
To enable or disable hardware acceleration:
- to check or uncheck the box: Options -> Advanced -> General-tab: Use hardware acceleration when available
- open/close Firefox completely.
- try the ajax grid page again
4 words:
Firefox Extended Support Release
Maybe what you need for your business is Firefox Extended Support Release ?:
http://www.mozilla.org/en-US/firefox/organizations/
Not sure why, but in my case the Ubuntu machine at home got the Firefox 15 release even before the Windows machine at work.
They actually fixed, many, many of these bugs.
This isn't just one bug, they fixed in this one release.
"I don't know of another code editor with this feature."
Cloud 9 IDE, a webbased IDE, does:
https://c9.io/site/features/
It's also an open source project:
https://github.com/ajaxorg/cloud9/
There are other I believe.
This is exactly why under the latest rules no rides in the peloton can have any injections what so ever. Obviously unless done so by a physician when there is a known problem.
Actually, this was on the first page of the article:
[ Move over, Amazon -- IaaS providers are elbowing into the cloud. [0] See how they compare in InfoWorld's slideshow. | Get the no-nonsense explanations and advice you need to take real advantage of cloud computing in the InfoWorld editors' "Cloud computing in 2012" PDF special report. [1] | Stay up on the cloud with InfoWorld's Cloud Computing Report newsletter. [2] ]
[0] http://infoworld.com/slideshow/57435/amazons-cloud-feels-the-heat-google-hp-microsoft-198319
[1] http://www.infoworld.com/d/cloud-computing/cloud-computing-in-2012-infoworld-special-report-187077 (free registration required)
[2] http://www.infoworld.com/newsletters/subscribe?showlist=infoworld_cloud_computing (free registration required)
I had a small look around, maybe this site will help too:
http://armservers.com/
How about this ?:
http://www.ztsystems.com/Default.aspx?tabid=1483
There is a big chance that will change in the future though. What do you think of Multi Path TCP ?
short demo:
http://www.youtube.com/watch?v=VWN0ctPi5cw
Longer presentation:
http://www.youtube.com/watch?v=02nBaaIoFWU
IETF WorkGroup:
http://datatracker.ietf.org/wg/mptcp/charter/
Linux kernel implementation:
http://mptcp.info.ucl.ac.be/
GoogleBot supports:
http://support.google.com/webmasters/bin/answer.py?hl=en&answer=35304
That is probably the one you are looking for.
Think of Larry Ellison as you think of a lawn mower:
http://www.youtube.com/watch?v=-zRN7XLCRhc#t=38m36s
Basically every program currently uses compositing (sometimes the toolkit/libraries does it for the program) or can easily do so.
Compositing seems to be the most efficient way to do it, but compositing was something that was added later to X as an extension.
They want to get rid of everything else in X and just use compositing as everything else can already be handled by the Linux kernel (this means wayland won't work for Unix as I understand it).
X just has a whole lot of legacy code and some overhead.
The reason why it is possible to build Wayland (replacing X is really big task) is because Wayland just does this small thing, compositing and all the other stuff can be handled by other parts of the system because in the years support for that has been added to the kernel or toolkit-libraries and so on.
The reason why Wayland does not do networking... is because again, other systems can handle that. RDP, X11, SPICE and even VNC.
Firefox and Chrome both have a stable API for addons (please stop calling it plugins ! Flash is a plugin), it is a X(HT)ML/JavaScript-only API.
The problem is Firefox didn't have that API at first, that API only came at a later point.
A lot of addons were made with the old API, which somewhat depend on the native API remaining stable.
Which it does, most of the releases.
The real problem is that there was only one indicator about the API to determine if the addon is compatible, which is the Firefox version-number.
That didn't fit well with the rapid release cycle.
But these problems have mostly been solved.