160 likes | 288 Vues
This document explores the integration of the Condor system into the mobile Internet landscape. It highlights goals such as improving user accessibility across various portable devices and examines mobile Internet technologies, including wireless systems and device hierarchies. Key architectural components of both web and WAP systems are discussed, alongside practical examples illustrating job submission and execution in Condor. The conclusion presents a usability hierarchy tailored for mobile devices, and outlines future work needed to enhance mobile computing functions.
E N D
Condor user interfaces for mobile terminals Javier Vales Alonso (jvales@delta.ait.uvigo.es) Javier González Castaño (javier@ait.uvigo.es) Universidad de Vigo (Spain)
Outline • Goals • Mobile internet & wireless technologies • Portable devices and their hierarchy • Web system architecture • WAP system architecture • Examples • Conclusions & future work
Goals • Integrate Condor in the mobile internet world. • Allow different levels of user accessibility. Or: ¿what is missing in Condor to face the mobile Internet?
Mobile Internet • Internet technologies and services for mobile devices. • Mobile-Internet is driven by the convergence of: • Wireless technologies • Portable devices
Wireless technologies • They will enable easy interconnection of a wide range of portable computing devices. • Present: 2G systems (GSM, IS-95). • Incoming: Wireless LAN (IEEE 802.11), Bluetooth, HomeRF, LMDS, 3G systems (UMTS).
Mobile devices • (Wireless) laptops (first mobile solution) • PDAs (Palm pilot, pocketPC,...): user interface with limited capabilities. Handwriting recognition. • WAP-enabled mobile phones: user interface even more limited. • Next: Wearable computers (less comfortable, need goggles). Speech recognition.
Condor Condor • Program tuning: • Final-stage programming utility • Small modifications in source code • Program generation • Check queue status • Remove, hold & release jobs • Submit new jobs • Alarm on job finish Usability • Check queue status • Remove, hold & release jobs • Submit new jobs • Program tuning +
Layer implementation • PDA layer is implemented as a web service. This has many advantages: • Familiar interface. • WAP system implementation is a subset of PDA system implementation (compatibility & reutilization) • Almost all PDAs have web browsers (platform independence) • WAP layer uses WML browsers.
Web system architecture HTTP Server 1. Operation request 3. Non-Condor command mapping 2. Condor command mapping CGI CGI HTML HTML Condor-enabled system Non-Condor commands Condor commands
WAP system architecture HTTP Server WAP G A T E W A Y 1. Operation request 3. Non-Condor command mapping 2. Condor command mapping CGI CGI WML WML Condor-enabled system Non-Condor commands Condor commands A L A R M
Conclusions & future work • Definition of usability-hierarchy for mobile internet devices • Assumption: Cell phone/PDA units everywhere • Remote execution of most functions • Other paradigms: Interface servers (X-Windows, Citrix)?