http://cricket.beboindia.com/india-vs-england-1st-odi-at-rajkot-live-streaming-video-live-scores.php

http://www.live-cricket-match.com/free-live-1st-odi-cricket-match-india-vs-england-online-tv-streaming.html

http://www.watchlivestream.tk/

Live Cricket on your Desktop

Hi Friends, just check dis out....its a cool thing
http://indiaforumstv.sportytube.net/2008/10/india-vs-australia-2nd-test-free-live.html

http://www.freedocast.com/DekhoMatch

Google Language Selector

http://labs.google.co.in/keyboards/gujarati.html

Google Translator

http://translate.google.com/translate_t#en|hi|

Avira Antivir VDF Updator

http://dl.antivir.de/down/vdf/ivdf_fusebundle_nt_en.zip

The power of Telemetics...

The automotive API will be an example for a convergence of heterogeneous industries : IT and automotive fields. The knowledge from the two fields should be closely streamlined with each other.

The API should provide a uniform way to handle the car devices such as door, speedometer, car diagnostics module and so on. Since there are various communication channels including GPIO, CAN, MOST, and so on, the API itself should provide an abstract way to be neutral to various configurations. GCF(General Connection Framework) introduced in J2ME can be used as an building block to implement the communication protocols. Furthermore, some kind of layered approach similar to communication protocol stack (logical device layer, physical device layer, and connection layer) might be necessary for this kind of abstraction. As a start point for the discussion to interface with car, the OBD-II specification (http://www.obdii.com) can be used to define the basic interface, because all cars in US have this interface by the regulation. A user could get status information about power train, engine, tiers etc. through embedded devices using API that based on the OBD-II standard.

JSR 172 web service API

This JSR is designed to provide an infrastructure as two optional packages for J2ME to:-

• provide basic XML processing capabilities
  
• enable reuse of web service concepts when designing J2ME clients to enterprise services
  
• provide APIs and conventions for programming J2ME clients of enterprise services
  
• adhere to web service standards and conventions around which the web services and Java developer community is consolidating
  
• enable interoperability of J2ME clients with web services
  
• provide a programming model for J2ME client communication with web services, consistent with that for other Java clients such as J2SE

The following technologies will be addressed:

• APIs for basic manipulation of structured XML data (parsing)
  
  • these APIs will be based around a suitable strict subset of the APIs already defined by JAXP
• APIs and conventions for enabling XML based RPC communication from J2ME, including
  • definition of a strict subset of the WSDL to Java mappings defined by JSR-101 (JAX-RPC), suitable for J2ME
  • definition of stub APIs based on the mapping above for XML based RPC communication, which will focus around subsetting the mapping and conventions produced by JSR-101.
  • definition of runtime APIs to support stubs generated according to this mapping supporting XML as a transport and encoding component
    
  • Investigation of a suitable and compact encoding mechanism for XML based RPC messages