Skip to main content

Faster internet! Coming soon to Asia (India)

image A few weeks back I wrote a comparison on prices for internet in India and the USA. Well, A lot is about to change. According to CNet news, a 7.68Tbps line is due soon to Asia. Bharati Airtel (one of the largest telecom companies in India) is part of the Unity Consortium which is making this happen.

According to the story,
The Unity Consortium, which consists of Google, Bharti Airtel, Global Transit, KDDI, Pacnet, and SingTel, has nearly completed the testing of the $300 million project. Internet users in Asia will start seeing faster Internet speeds over the next several months from the new cable, which has the potential to create a 7.68Tbps (terabits per second) connection under the Pacific.
This could mean a lot of change in dynamics and economics of internet traffic. With already (considerably) low prices in India (thanks to a tough competition among BSNL, Reliance, Airtel and Tata), The only complaint was the speeds of unlimited plans. A limit-less user, generally capped by a speed of 512kbps, is almost never a happy YouTube viewer. Speedy lines like these would allow more bandwidth to the end users. The effect will trickle down to prices and a tougher competition.

India's Wimax (Apollo, Hathway, BSNL) and Wireless (read Tata PhotonPlus, Reliance NetConnect)  Internet markets will also have tougher competition from their wired line counterparts. This market is already very inexpensive when compared to options available in USA.

Mobile Internet, TRAI's futuristic IP Telephony will be a interesting watch following this development.

All in all, Its a welcome trend. India must now work more on expanding its internal infrastructure.

Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>