The Funambol J2ME Mail Client aims to be a light, easy to use, free email
client for J2ME devices.
The first release comes with a simple but effective UI, and a storage limited
to the internal RMS only. This makes the application compatible with most of
the phones around (minimum requirements are: MIDP2.0, CLDC 1.0, 512k of
Storage).
The mail synchronization using SyncML 1.2 over HTTP, thus removing
any problem related to the access to IMAP or POP ports.
The mail client synchonizes its address book with the one on the server,
Its design is modular and can be extended in future with other mail
protocols, a more sophisticated UI and access to the phone s AddressBook or
filesystem for the devices allowing this.
See the javadoc for more information on the structure of the library.
Sector is a system infrastructure software that provides functionality for distributed data storage, access, and analysis/processing. It automatically manages large volumetric data across servers or clusters, even those over distributed wide area high speed networks. Sector provides simple tools and APIs to access and/or process the data. Data and server locations are transparent to users, as the whole Sector network is a single networked super computer to the users.
Addfilter is a command-line application which adds and removes filter drivers for a given drive or volume. It is intended to demonstrate how to insert a filter driver into the driver stack of a device. The sample illustrates how to do this by using the SetupDi APIs. The sample works on the x86 platform. It has only been tested in a 32-bit environment. Since Addfilter is not a driver, it does not deal with Plug and Play or Power Management.
Addfilter is a command-line application which adds and removes filter drivers for a given drive or volume. It is intended to demonstrate how to insert a filter driver into the driver stack of a device. The sample illustrates how to do this by using the SetupDi APIs. The sample works on the x86 platform. It has only been tested in a 32-bit environment. Since Addfilter is not a driver, it does not deal with Plug and Play or Power Management.
No INF file is needed to install this application.
Abstract—Wireless networks in combination with image
sensors open up a multitude of previously unthinkable sensing
applications. Capable tools and testbeds for these wireless image
sensor networks can greatly accelerate development of complex,
yet efficient algorithms that meet application requirements. In this
paper, we introduce WiSNAP, a Matlab-based application
development platform intended for wireless image sensor
networks. It allows researchers and developers of such networks
to investigate, design, and evaluate algorithms and applications
using real target hardware. WiSNAP offers standardized and
easy-to-use Application Program Interfaces (APIs) to control
image sensors and wireless motes, which do not require detailed
knowledge of the target hardware. Nonetheless, its open system
architecture enables support of virtually any kind of sensor or
wireless mote. Application examples are presented to illustrate the
usage of WiSNAP as a powerful development tool.
This book shows you how to write programs that run under Microsoft Windows 98, Microsoft Windows NT 4.0, and Windows NT 5.0. These programs are written in the C programming language and use the native Windows application programming interfaces (APIs). As I ll discuss later in this chapter, this is not the only way to write programs that run under Windows. However, it is important to understand the Windows APIs regardless of what you eventually use to write your code.
This document accompanies a sample co-installer that can be used in conjunction with an INF file to install additional device INF files on the target system during a device installation. The instructions herein apply to the Microsoft Windows 2000 and Windows XP and Windows Server 2003 operating systems.
The sample co-installer described in this article interprets CopyINF directives in a [DDInstall] section in an INF file. The sample demonstrates using a co-installer to perform processing after a device has been installed, parsing the INF section that is being used for the installation, and the use of the SetupCopyOEMInf, SetupGetInfInformation, SetupQueryInfOriginalFileInformation and SetupDiGetActualSectionToInstall APIs.
