Call history for Java Midlet - prototype and report

The purpose of this project is to demonstrate the usage of the PIM API and MIDlet record store in Java Midlets (J2ME). To deliver a working prototype and a report with tips and tricks for PIM API use. An initial prototype of the Java midlet is provided and can be used as base. This prototype may be run in a simulator and emulates a client that sets up IP phone calls. However, the main goal of this project is to maintain call history in three different ways using the MIDlets record store and PIM API. Implementation Following choices describe the different implementation of the call history handling. 1) No PIM used Use record store to store last x calls (phone numbers) made by the user. The size of that list should be configurable (using static member) as maximum space allowed in the RS differs between handsets. 2) PIM (read only) Same as choice 1 but synchronizes its call history with the handsets built-in call log. This means that the call history in the midlet will show calls made from the midlet along with calls made outside the midlet (not wise-wersa). 3) PIM (read-write) Same as choise 2 but the call history is synchronized both ways. This means that the call history in the midlet is synchronized with the handsets built-in call log and wise-wersa. Project Delivery Delivery package must fulfill and include:  Three seperate implementations of the call history described in options 1-3.  All classes and methods documented.  A report listing: 1. How PIM is installed to handsets along with the MIDlet. Specify other APIs that are required, if any. 2. Possibilities/limitations of the PIM API. 3. Supporting handsets and complexity in terms of implementation and OTA intallation on handsets. 4. Personal evaluation. More information e.g. on simulator is in attached .zip file. ## Deliverables 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables): a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment. b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request. 3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement). ## Platform The program needs to run on no less then Java Midlet simulators e.g. Sun simulator.