Monday, June 16, 2008

One of the reasons why Blogger code is so "unstable" (judging from the threads in the help forums) is that, as I wrote long ago, it involves code and data that starts on Blogger computers ("servers"), but is processed from other computers ("owned" by bloggers) which are connected to the Blogger computers over networks that nobody owns or controls.

Some of these factors Blogger can accept responsibility for. Others we (the blog owners, or blog readers) have to accept responsibility for. And still others are the fault of the network owners, and many of those are problems which nobody will accept responsibility for.

And that's the problem with diagnosing the ever common bX- codes. Of late, some bloggers are pumping themselves up, and declaring to the world
Finally the solution to the BX error codes of blogger.com

Don't know who and why it works and why google/ blogger have failed to recognize such simple tricks. But still that doesnt reduce its efficacy..
as if they themselves developed the simple process of clearing cache and cookies.

The frustrating part of this is that, in a very limited number of cases, clearing cache and cookies may produce positive results. But using that procedure as a general solution is so wrong, because it's limited to very specific scenarios. We need to understand the scenarios which generate the codes, before we can truly understand this.

>> Top

Elm0D

Author & Editor

Has laoreet percipitur ad. Vide interesset in mei, no his legimus verterem. Et nostrum imperdiet appellantur usu, mnesarchum referrentur id vim.

0 comments:

Post a Comment

Navigate» Become author for this Blog

Manual Categories