Skip to main content

LATEST GOOGLE PROJECTS

PROJECT LOON

 



Google’s Project Loon aims to provide internet services all over the world with ring of  Balloons that will fly around the globe on the stratosphere above earth surface.
The goal of the Google’s Project Loon is to provide internet services in rural and remote areas where people are still unaware of internet benefits. The project loon will help in filling coverage gaps and will bring people back online after disaster.

How Google’s Project Loon works:

 

 The project loon balloons fly 20km above earth surface in the stratosphere. In stratosphere there are several layers of winds and each layer of wind have different direction and speed. The software algorithm will find out the right direction for the Loon balloons. Balloons will choose the right layer and moves towards right direction. The Loon balloons can be arranged to form a communication network. People can connect to the network by special antenna attached to their respective buildings.

PROJECT GOOGLE GLASS

 Glass is smart eye wear that helps you get exactly what you want, in the moment. Search, photos and videos, messaging, apps and more.

 Project Green Energy

 

At Google, people strive to power their company with 100% renewable energy. In addition to the environmental benefits, they see renewable energy as a business opportunity and continue to invest in accelerating its development. 
 They are testing new renewable energy technologies on their campuses,evaluate them against a few criteria: They must make good business sense, have potential for long-term significant impact and transform the industry.

Comments

Popular posts from this blog

SQL Server

                                                                     SQL Server  Its been a while that I have updated my blog. Though Databases and SQL was something that I used to stay away as much as possible because for some reasons, I got to work on these all the day for 8-9 hours and sometimes haunting in the nights and weekends as well. However, it has been a good journey so far and I found some interesting stuff in SQL Server. So, this triggered an idea a couple of weeks back to share some cool stuff that I am learning in SQL Server over numerous sources. Hope I can make this a good series. As there are not much visitors to my blog, le...

An TLS 1.2 connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server. The TLS connection request has failed.

If the certificate being used on the server was generated using the Legacy Key option in the certificate request form, the private key for that certificate will be stored in Microsoft's legacy Cryptographic API framework. When the web server tries to process requests using its new, Cryptographic Next Generation (CNG) framework, it appears that something related to the RSA private key stored in the legacy framework is unavailable to the new framework. As a result, the use of the RSA cipher suites is severely limited. To avoid the issue, you can try to generate the certificate request using the CNG Key template in the custom certificate request wizard.

Remote Login Failure on Server

I ran into an interesting situation when executing a Remote Stored Procedure on Linked   Server using four part query.    Vista-3139 which is a SQL Server 2005 instance is linked to the SERV2003\SQLDUMMY which is a SQL Server 2000 named instance. When I tried to execute a stored procedure: EXEC [SERV2003\SQLDUMMY].SQLAdmin.dbo.sp_ddlevents   Got the following error message. Could not connect to server SERV2003\SQLDUMMY ' because '' is not defined as a remote login at the server. Verify that you have specified the correct login name. I checked the Security settings of the linked server and it was set to “Be made using the login's current security context", which is valid considering that the user has all the permissions to login to the remote SQL server. Then I changed the security context to use a SQL authentication, but still it failed with the similar error message as described above. To troubleshoot this further, I ran...