Skip to main content

The Indian Broadband Policy 2004

The Indian Broadband Policy 2004, the drawing board of India's digital future was announced sometime ago. According to the preamble,
Recognising the potential of ubiquitous Broadband service in growth of GDP and enhancement in quality of life through societal applications including tele-education, tele-medicine, e-governance, entertainment as well as employment generation by way of high speed access to information and web-based communication, Government have finalised a policy to accelerate the growth of Broadband services.
Broadband has huge potential to bring about far reaching changes in far flung regions of India. Besides revolutionizing entertainment and communication, it can pave way towards better standards of educaton and healthcare with telemedicine and distance education programs for those in the remotest of areas.

But how do we achieve a 'ubiquitous Broadband service'? The sad reality as of now is that connectivity remains a major problem of India. The cost of bandwidth is on the higher side and as result of these, the 'broadband experience' remains restricted to a few of its huge population. Does this policy address these issues? Disappointingly, No.

Comments

Popular posts from this blog

Gmail Chat Disabled

The fact that it happened does not surprise me but that it took so long for our network administrators to figure it out does. And if you are wondering how do you disable Gmail's chat features on your network, you only need locking DNS lookups to chatenabled.mail.google.com , by returning 127.0.0.1 .

Advertising Billboards as Rain Covers

Advertising billboards are put to use as Pakistani refugees, left homeless after the October 8 earthquake, set up their tents in Muzaffarabad, Pakistan. [via SFGate ] Technorati Tags: Pakistan Earthquake

Community effort to create a single persistence model for the Java community

A community effort led by Sun Microsystems is aiming to create a single 'Plain Old Java Object' persistence model to provide a single object/relational mapping facility for Java app developers in J2SE and J2EE. Paul Krill writes In a letter to the “Java Technology Community” on Friday, specification leads on Java Specification Request (JSR) 220, which is the proposal for Enterprise JavaBeans 3.0, and JSR-243, for Java Data Objects, state that the two technologies feature divergent persistence models. “This divergence has caused confusion and debates among Java developers, and is not in the best of interest of the Java community,” said JSR-220 leader Linda DeMichiel who also is a Sun employee, and Craig Russell, a staff engineer at Sun who leads JSR-243. “In response to these requests [for an end to the unwanted divide], Sun Microsystems is leading a community effort to create a single POJO (Plain Old Java Object) persistence model for the Java community,” the letter said.