Trip to Riverston and Wasgamuwa

Mobile ATM

As a result of industry revolution and globalization, usage of money in the society is increased. But people realized that using large amount of money is a risky task. As a solution they started using banking facilities for money transactions. At the moment banks provide more interactive facilities for efficient money transactions. However unfortunately there are so many problems related to bank transactions. In developing countries these problems become worst. During last decades researchers try to apply information and communication technology to solve above problems. They introduced E- commerce and M-commerce. Some of the solutions are ATM services, credit card/debit card services and so forth. But using and implementing these IT base solutions in developing countries is a big challenge due to poor IT infrastructure. But most developing countries like Sri Lanka, mobile telecommunication sector archive rapid expansion. As IT researchers in developing countries, we have to think of new money withdrawal/deposit system (ATM system). That system would be enable people to perform ATM transactions based on mobile technologies. Proposed Mobile ATM system will reduce some barriers of using ATM and improve security related to ATM.

Moblie Trends

Use Same AJAX Code In Your Moblie

Abstract

Developing AJAX programs for mobile devices is not an easy task. The objective of this project is extending the GWT UI library functionalities to make developers’ work easier. It provides functionalities to reuse the same AJAX code (with minor changes) in desktop browsers as well as in mobile browsers. This extended GWT will be an interesting tool for developers, which keep them away from complex low-level Ajax development for mobile devices using JavaScript.

Description

Different mobile browsers have different capabilities and behaviors, for example the way browser modifies its layout based on orientation of phone layout etc. Also the behaviors of the desktop browsers and mobile browsers are different. This means some the objects in web GUI will display same in both browsers, such as “Labels” and some objects will completely different from desktop web interfaces. Not only that, mobile devices are less in processing power than desktop web interfaces. So some objects which involve more processing power should not enable in mobile browser.

Hence, after doing some researches in order to understand the best way of improving efficiency of the mobile browsers, this project will be attempt to implement the required features in GWT.

Main Components

This system should have a mechanism to identify the status of the browser which the request coming from. Whether it is a desktop browser or mobile browser as well as it should identify the capabilities of the client browser.

Server/client DOM

Traditional applications deliver server-side changes to the client browser, where full page refresh occurs. With this GWT component all the server-side processing occurs in to the server side DOM. Only updates are delivers to the client browser. In the client also have client side DOM. This is responsible for detecting user interaction in client browser, and delivering user data to server for processing.

AJAX Broker

AJAX broker coordinates both server-side program and client browser. AJAX broker go through the DOM (client or server side) and filter out the changes of the DOM. Only the changes are submitted to server/client. Therefore developer should not work with low level implementation of AJAX communication.