A TRANSPORT LAYER PROTOCOL

The Jitter Block Transfer protocol was designed and developed by Jeffrey Brandon Turner in 2007, following a 5 year effort to create the Rich Internet Media application Protocol - RIMP.  While its name intentionally matches the initials of the inventors' name, it was chosen because it provides interference and fluctuating connectivity correction with the use of dynamically allocated data blocks throughout transmission.  This in contrast to the widely used, 25 year old Transmission Control Protocol or TCP, that sets block size and transmission rates at a fixed interval based on worst-case determination at initial connection (FYI: "known as sliding window technique").  TCP was design for tightly coupled local area networks (LANs) with persistent and consistent connections.  JBT however was designed for wireless and mobile connections that are known to suffer from frequent communication jitters.  JBT is a transport layer service created in response to increasing demands of rich media transport as originally outlined as an industry problem in Mr. Turner's WebOS Manifesto. Turner, J. (2003). WebOS Manifesto. Roscoe, IL USA (p. 7).

At its core, JBT is based on UDP, providing a simple transport layer direct socket connection that can quickly and easily communicate between client and server as to the status of the connection, integrity of data and for the exchange of key information about the connection needed to determine the next set of blocks to transfer.  JBT also uses UDP to punch a whole through Firewalls/Gateways and to mask as UDP, so that existing systems do not require modification to use JBT.  To best understand the technology of JBT, a whimsical vernacular was created to identify the parts of JBT, based on firearms.  In practicality the vocabulary of JBT also helped organize the many complex features of JBT otherwise abstract.  See Glossary of Terms.

INSPIRED BY RIMP

Early prototypes of RIMP (definition of RIMP) (definition of Rich media) used TCP as the transport layer service.  Many of the ideas and benefits of RIMP however were underutilized and often overshadowed by failures in performance by TCP in certain situations.  It soon became apparent why TCP Accelerators and most new breeds of communication software based on TCP, seem to hit basic limits.  The aging TCP simply was not designed for Rich Media delivery over today's diverse Internet networks.  The solution was not to patch or enhance TCP, rather to replace it.  Free from the limits of TCP, RIMP would be able to introduce techniques that when combined, created an awesome Internet experience.  Inspiration for JBT was drawn from examining the barriers in the TCP based RIMP, the missing functionality of TCP, and many UDP based techniques common in file sharing applications.

A PROTOCOL SUITE - RIMP/JBT/IP

RIMP is the Application/Session layer protocol designed to be integrated into a web browser to service all web browser communication needs.  JBT is the work-horse of RIMP, providing the actual packaging and transmission of data to the IP layer, and eventually to a destination device.