Tech Trek: A Software Engineer's Guide to Code and Beyond

This is tutorial assumes you already have Eclipse installed. You can install the any plugin for Eclipse using the Software Update feature of Eclipse. To install the plugin, using Eclipse: Select the Help menu > Install New Software. ... In the Work with text box, enter: For Subversion: http://subclipse.tigris.org/update_1.0.x For Android: https://dl-ssl.google.com/android/eclipse/ For Google App Engine: Eclipse 3.6 (Helios): http://dl.google.com/eclipse/plugin/3.6 Eclipse 3.5 (Galileo): http://dl.google.com/eclipse/plugin/3.5 Eclipse 3.4 (Ganymede): http://dl.google.com/eclipse/plugin/3.4 Eclipse 3.3 (Europa): http://dl.google.com/eclipse/plugin/3.3 Click OK In the Available Software dialog, select the checkbox next to Developer Tools and click Next. In the next window, you'll see a list of the tools to be downloaded. Click Next . Read and accept the license agreements, then click Finish . No...

The Third Party Server is *your* server and can actually be any process written in any language (for example, it can be a batch process or a cron script). The role of the 3rd party "server" is to send the message to the device. The Server will store (or update) the registrationID received into its local database. So, eventually the server will have registrationIDs from the devices. Your server needs to get a ClientLogin Auth token in order to talk to the C2DM servers. When it wants to push a message to the device. For ClientLogin Auth_Token:  Click Here To send a message to a particular device, the Server needs to POST to the C2DM Service the following 4 things:  The accountName which will be arxxus.pushapp@gmail.com . An authentication Token. The registrationID of the device it wants to send the message.  The message itself (Message limit 1024 Bytes) Code: // Create a new HttpClient and Post Header  HttpClient httpclient = new DefaultHttpClient()...

Google offers a cloud computing infrastructure called Google App Engine (App Engine) for creating and running web Applications. App Engine allows the dynamic allocation of system resources for an application based on the actual demand. Currently App Engine supports Python and Java based applications. But Google App engine have some Restrictions GoogleApp Engine runs a version of Java 6 but does not provide all Java classes, for example Swing and most AWT classes are not supported. You cannot use Threads   or frameworks which uses Threads. You can also not write to the filesystem and only read files which are part of your application. Certain "java.lang.System" actions, e.g. gc() or exit() will do nothing. You can not call JNI code. Reflection is possible for your own classes and standard Java classes but your cannot use reflection to access other classes outside your application. A servlet needs also to reply within 30 seconds otherwise a com.google.apphosting.api.Dead...

Before you can write client applications that use the C2DM feature, you must have an HTTPS application server that meets the following criteria:Able to communicate with your client. Able to fire off HTTP requests to the C2DM serve r. Able to handle requests and queue data as needed. For example, it should be able to perform   exponential back off.  Able to store the ClientLogin Auth token and client registration IDs. The ClientLogin Auth token is included in the header of POST requests that send messages. For more discussion of this topic, see  ClientLogin for Installed Applications . The server should store the token and have a policy to refresh it periodically. The ClientLogin authorization process: Authorization with ClientLogin involves a sequence of interactions between three entities: the installed application, Google services, and the user. This diagram illustrates the sequence: When the third-party application needs to access a user's Googl...