Showing posts with label javascript. Show all posts
Showing posts with label javascript. Show all posts
Sunday, 23 March 2014
Saturday, 8 March 2014
[SCRIPT] How to perform bulk posting to Blogger via Google Blogger API without Client and
Note that you should get your Blogger API Key at Google API Console.
Blogger API is experimental AND must be requested explicitly.
But getting the Auth key from the Headers of the Google Blogger Developers Documentation and performing the OAuth login, you'll be able to perform calls to the REST API.
Blogger API is experimental AND must be requested explicitly.
But getting the Auth key from the Headers of the Google Blogger Developers Documentation and performing the OAuth login, you'll be able to perform calls to the REST API.
Tuesday, 21 July 2009
Firefox 3.5.1 still exposing bugs
Firefox 3.5.1 represents a step towards a faster browser.
Several benchmarks show Safari 4, Opera 10 and Chrome as the fastest browsers on the market - I heard "Webkit rules" - and they only seem to lack in the plug-ins feature.
I'm not taking into account IE X.x because... I think it already exists only because is bundled into the most common OS in the world. And there's no reason to use it.
Anyway... After the first exploit (more here) soon patched by Mozilla team, we got a bug in JavaScript engine, not well managed in 3.5.1.
The issue is well described here and this time it is not useful for executing code (at the moment), but "only" for a DoS.
Possible workaround? Disable JavaScript, No-Script plug-in or switch to the older JavaScript engine from about:config, disabling javascript.options.jit.content. Choosing the 3rd option, there will be a drop in the overall performances of Firefox.
Several benchmarks show Safari 4, Opera 10 and Chrome as the fastest browsers on the market - I heard "Webkit rules" - and they only seem to lack in the plug-ins feature.
I'm not taking into account IE X.x because... I think it already exists only because is bundled into the most common OS in the world. And there's no reason to use it.
Anyway... After the first exploit (more here) soon patched by Mozilla team, we got a bug in JavaScript engine, not well managed in 3.5.1.
The issue is well described here and this time it is not useful for executing code (at the moment), but "only" for a DoS.
Possible workaround? Disable JavaScript, No-Script plug-in or switch to the older JavaScript engine from about:config, disabling javascript.options.jit.content. Choosing the 3rd option, there will be a drop in the overall performances of Firefox.
Tuesday, 2 September 2008
Google Chrome
... Unexpected news from big G ...
Google Chrome will be released as Beta version within few hours from now.
Some features I caught on the net seem to be:
Google Chrome will be released as Beta version within few hours from now.Some features I caught on the net seem to be:
- optimized "Task - Process" management
- optimized JavaScript engine
- uses WebKit (as Safari and the Android Browser)
- designed from scratch, based on nowadays needs
- optimized Garbage collector
- (?) maybe based on VMs
Subscribe to:
Posts (Atom)