Judge who said 'Rathore being harassed'

A shocking conflict of interest has come to the fore n the Ruchika Girhotra molestation case. The presiding judge was in fact, Ruchika's next door neighbour and is said to be harbouring some amount of hard feelings towards Ruchika's family. However, Judge Khaturia of the Punjab and Haryana High Court -- the man responsible for the meager 6 month sentence handed to ex DGP SPS Rathore, seemed to be more concerned about the accused rather than the victim. Justice Khaturia contended that it was Rathore, who was being harassed. Speaking to TIMES NOW, Ruchika's friend Adhunika made the shocking revelation saying, "Khaturia, who was the judge of HC, who dropped the charges of Section 306, you would be amazed to know that he was the next door neighbour of Ruchika. Knowing that, Khaturia knows that if you know a person you are not allowed to make any judgement in that case. He not only gave the judgement, but also dropped the charges of abetment to suicide." "It was some political interference or SPS Rathore's influence. If you know somebody, even if he or she is your neighbour, you cannot give any bias decision. Either he should have sent this to some other judge or done something about it," added Adhunika. Copy rights by google

IP Addresses and Domains of Google's Data Centers

The progression of a Google Dance could basically be watched by querying the IP addresses of Google's data centers. But queries on the IP addresses are normally redirected to www.google.com. However, Google has domains which resolve to the single data centers' IP addresses. These domains as well as their IP addresses are shown in the following list.

Domain	IP-Adresse
www-ex.google.com	216.239.33.100
www-sj.google.com	216.239.35.100
www-va.google.com	216.239.37.100
www-dc.google.com	216.239.39.100
www-ab.google.com	216.239.51.100
www-in.google.com	216.239.53.100
www-zu.google.com	216.239.55.100
www-cw.google.com	216.239.57.100
www-fi.google.com	216.239.41.100
www-gv.google.com	216.239.59.100
www-kr.google.com	66.102.11.100
www-mc.google.com	66.102.7.100
www-lm.google.com	66.102.9.100

Those that keep an eye on Google's index updates often think that the Google Dance is over, when they see the new index at www.google.com or when they don't see the old index at www.google.com for some time. In fact, the update is not finished until all the domains listed above provide results from the new index.
The index updates at the single data centers seem to happen at one point in time. As soon as one data center shows results from the new index, it won't switch back to the old index. This happens most likely because the index is redundant at each data center and at first, only one part of the servers (eventually half of them) is updated. During this period, only the other half of the servers is active and provides search results. As soon as the update of the first half of servers is finished, they become active and provide search results while the other half receives the new index. Thus, from the user's perspective, the update of one data centers happens at one point in time.
Finally, it shall be noted that the access to the single data centers is generally controlled by the DNS only, but sometimes queries are redirected. However, this is easy to detect: When for a query at one of the domains listed above, the links to Google's cache do not comply with the IP address that belongs to the domain, then the query is redirected. If this happens, Google inhibits - for whatever reason - the access to one data center.

Copy rights by google

 putas valencia  putas sevilla

Google Dance and DNS

Not only Google's index is spread over more than 10,000 servers, but also these servers are, as of now, placed in 13 different data centers. These data centers are mainly located in the US (i.e. Santa Clara, California and Herndon, Virginia) and in Dublin, Ireland.
In order to direct traffic to all these data centers, Google could thoeretically record all queries centrally and then send them to the data centers. But this would obviously be inefficient. In fact, each data center has its own IP address (numerical address on the internet) and the way these IP addresses are accessed is managed by the Domain Name System.
Basically, the DNS works like this: On the Internet, data transfers always take place in-between IP addresses. The information about which domain resolves to which IP address is provided by the name servers of the DNS. When a user enters a domain into his browser, a locally configured name server gets him the IP address for that domain by contacting the name server which is responsible for that domain. (The DNS is structured hierarchically. Illustrating the whole process would go beyond the scope of this paper.) The IP address is then cached by the name server, so that it is not necessary to contact the responsible name server each time a connection is built up to a domain.
The records for a domain at the responsible name server constitute for how long the record may be cached by a caching name server. This is the Time To Live (TTL) of a domain. As soon as the TTL expires, the caching name server has to fetch the record for a domain again from the responsible name server. Quite often, the TTL is set to one or more days. In contrast, the Time To Live of the domain www.google.com is only five minutes. So, a name server may only cache Google's IP address for five minutes and has then to look up the IP address again.
Copy rights by google
putas madrid    putas barcelona

Google Dance - The Index Update of the Google Search Engine

The name "Google Dance" has often been used to describe the index update of the Google search engine. Google's index update occurred on average once per month. During an index update there was significant movement in search results and Google showed new backward links for pages. However, in mid-2003 Google started to update it's index continuously. It appears that, still, there has to be an update of the complete index once in a while and during this time new backward links are shown. But, because of the continuous update, the effects on search results seem to be rather insignificant.

We will keep this site up running because it provides some information beyond the Google Dance. But there will no longer be a monitoring of updated data centers during a "Dance".
copy rights by google
escorts barcelona     escorts valencia     escorts sevilla

Google Analytics Update

 
<!-- @page { margin: 2cm } P { margin-bottom: 0.21cm Google Analytics team is constantly working to release new
features and fix known issues to give you a better experience. This
page is frequently updated for your information and benefit. You can
also check out the official Google Analytics Blog for
up-to-the-minute news about Analytics (in English or French only).


Browse through a catalog of our biggest updates below:
August 2009
The ga.js release notes are finally here! Below you’ll find
everything you need to know about udpates to the ga.js code
including:

• Proper encoding for search terms for organic searches, web page path info for (utmp), and user defined values when used with the linker feature.
  
• The search engine Rambler is added to the organic search list
  
• Organic search parsing is corrected for search engine http://kvasir.no
  
• New organic search engines defined by the user now added to the top of the list
  
• Removed deprecated _trackEvent(action, label, value) function and replaced it with _trackEvent(category, action, label, value)
  
• Referrer URLs are now stored as case sensitive. For example: www.domain.com/PaGe.HtMl will be reported with case information.
  
• Added a 1200 character limitation to GASO token size.
  
• New function was added to allow overriding the default timeouts for cookies ( set Cookie Persistence(time-out)) 

    copy rights by google

• escorts madrid