This paper presents several low-latency mixed-timing
FIFO (first-in–first-out) interfaces designs that interface systems
on a chip working at different speeds. The connected systems
can be either synchronous or asynchronous. The designs are then
adapted to work between systems with very long interconnect
delays, by migrating a single-clock solution by Carloni et al.
(1999, 2000, and 2001) (for “l(fā)atency-insensitive” PROTOCOLS) to
mixed-timing domains. The new designs can be made arbitrarily
robust with regard to metastability and interface operating speeds.
Initial simulations for both latency and throughput are promising.
rdesktop is a client for Microsoft Windows NT Terminal Server, Windows 2000
Terminal Services, Windows 2003 Terminal Services/Remote Desktop, Windows XP
Remote Desktop, and possibly other Terminal Services products.
rdesktop currently implements the RDP version 4 and 5 PROTOCOLS.
Universal Serial Bus (USB) is a communications architecture that gives a personal
computer (PC) the ability to interconnect a variety of devices using a simple four-
wire cable. The USB is actually a two-wire serial communication link that runs at
either 1.5 or 12 megabits per second (mbs). USB PROTOCOLS can configure devices
at startup or when they are plugged in at run time. These devices are broken into
various device classes. Each device class defines the common behavior and
PROTOCOLS for devices that serve similar functions. Some examples of USB device
classes are shown in the following table
This document outlines what is necessary to install and run the LEACH protocol on version
2.27 of ns2. At the time of this writing, this is the newest version of ns2. The LEACH implementation
was written as a stand-alone application. Thus, in the past a version compiled for LEACH may or may
not work for other PROTOCOLS. In addition, the original version of LEACH was compiled for version
2.5b which is an outdated version of ns2.
This article describes a sniffer for Windows. WinSniff is an application for capturing packets on the network. It displays all the packets that are transmitted on the local network and gives detailed information about each header in the packet. In order to keep it simple, I am not dealing with application level PROTOCOLS. If you are interested, you can add features to support various application level PROTOCOLS such as SMTP, FTP, NETBIOS etc
C++ class libraries for network-centric, portable applications, integrated perfectly with the C++ Standard Library. Includes network PROTOCOLS (Sockets, HTTP, FTP, SMTP, POP3, etc.) and an XML parser. Licensed under Boost license.
A distributed, peer-to-peer, server-less communication & messaging solution for JAVA (JMS), C++ and .NET applications, integrates with JBoss, WebLogic & WebSphere. Offers guaranteed delivery, security and transactions. Supports TCP, SSL & HTTP PROTOCOLS
3.1 Data Link Layer Design Issues
3.2 Error Detection and Correction
3.3 Elementary Data Link PROTOCOLS
3.4 Sliding Windows PROTOCOLS
3.5 Protocol Specification and Verification
3.6 Example Data Link PROTOCOLS
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.
As science advances, novel experiments are becoming more and more complex, requiring a zoo of control devices and electronics executing complicated sequences of steps. Device availability and monetary constrains usually lead to a highly heterogeneous setup with components from several different manufacturers using many different PROTOCOLS and interfacing mechanisms. This often results in control software being puzzled together to use and provide a multitude of interfacing and control functionality, each using their own calling conventions, data structures, etc. To make matters worse, usually a group of relatively independent programmers is trying to write and maintain the code base. Often this causes extensive duplication of effort as program segments are hard to reuse, since unpredictable changes to the segments by the original authors might compromise other code using these segments.
