Examples - Network Communication Software

More often than not, today's applications require communications to other software and/or the Internet.  To do this requires the ability to use protocols, and create client & server programs.  Part of my most recent project to create better communication protocols at SymbiontWeb; I created a client and server application to harness them.

 

Called, the Webby Network; it is a communication system designed to improve the transmission of digital data & media over the Internet for rich Internet applications (RIA). The Webby Network replaces HTTP, FTP, and native streaming methods used by computer browser systems, for a faster, more secure and reliable connection. The Webby Network technology is best used in applications where limited bandwidth and/or high volume of information are expected.

 

Key areas within the Webby Network technology are:

·        Rich Internet Media Protocol, RIMP which replaces HTTP (normal browser protocol)

·        Reflection (improves media downloading and processing performance)

·        Normalization (improves the connection)

 

Application of the Webby Network Technology

The Webby Network communication system can be applied to desktop and portable systems.  The technology is currently designed for Windows and Linux operating systems on the client and server; with designs to expand the technology into the MacOS and PalmOS.  Here are the benefits of utilizing the Webby Network technology for RIA's.

 

Benefits for devices on stable connections (typically desktop systems)

ü      A series of asynchronous bi-directional information channels that allow for the transfer of information without disrupting normal page or file transfers.

ü      A faster HTTP based channel for web page transfers that allows for the transfer of pages without disrupting the file channel and utilizing a process named "Reflection".

ü      Reduction of browser and protocol overhead utilizing the Client-Side Reflection technology - which also improves client-side browser script execution.

ü      Reduction of unnecessary data transport and increased availability of information by utilizing the Server-Side Reflection technology.

ü      Asynchronous bi-directional streaming file transfer that allows for the transfer of files without disrupting normal page transfers.

ü      Transparent compression of all non-compressed data

ü      A modulating encryption scheme

 

Benefits for devices on unstable connections (typically mobile and laptop systems)

ü      Faster and more consistent information transfer over low-band connections and/or inconsistent connections utilizing the "Normalization" technique - which is ideal for mobile devices out of range from 3G or Wi-Fi connectivity.

ü      A series of asynchronous bi-directional information channels that allow for the transfer of information without disrupting normal page or file transfers.

ü      A faster HTTP based channel for web page transfers that allow for the transfer of pages without disrupting the file channel and utilizing a process named "Reflection".

ü      Reduction of browser and protocol overhead utilizing the Client-Side Reflection technology - which also improves client-side browser script execution.

ü      Reduction of unnecessary data transport and increased availability of information by utilizing the Server-Side Reflection technology.

ü      Asynchronous bi-directional streaming file transfer channels that allow for the transfer of files without disrupting normal page transfers.

ü      Transparent compression of all non-compressed data

ü      A modulating encryption scheme

 

The Webby Network technology is applied as a client application named the "Webby Client"; a transfer protocol named "RIMP" which sits on top of the existing HTTP protocol; and a server application named "Webby Server". The client application is primarily responsible for providing RIMP on the client device, whereas the server application is primarily responsible for administering RIMP on the hosting device. As A standard, each application is independent of the browser and services other functions other than RIMP support; including system I/O access and attached application execution, explained later in this document.

 

Devices with limited available runtime memory (e.g. less than 5MB's free); typically found in late model Smartphones and PocketPC's, require the use of a browser plug-in variant of the Webby Client, rather than the standard Webby Client application. Devices with insufficient runtime memory usually are unable to keep the standard application loaded and running as the OS runs out of memory and shuts down the service.  The plug-in variant is only active as the browser is loaded and remains in memory even as the OS closes other applications.  The application has a smaller footprint in memory however, has few available services than the standard application.  The stand-alone application is preferred because it allows the device to work asynchronously from the browser on the Webby Network; especially important for persistently connected desktop systems exposing files for remote access.
 

 
  Home |  Shop |  Projects |  Skills |  My Lab |  WebOS |  Mobile |  Websites