One of my more prolific and recent projects has been the creation of an alternative protocol suite to the ageing HTTP/TCP/IP suite. Why? - To improve speed, performance and reliability! HTTP was not designed for the size, complexity and richness found in today's web pages. I doubt its designers could have imagined how successful and far reaching HTTP would become; otherwise they might have added the necessary functionality to support rich media. As a consequence, thousands of augmenting technologies, tools, and scripting languages have evolved to extend HTML. AJAX, DHTML and indeed, CSS, are direct inventions that have grown out of the limitations of HTTP and HTTP's synonymous counterpart, HTML. Due to the enormous adoption of HTTP, little can change as it is necessary to persist to support legacy systems. What is needed is a protocol based on HTTP that could support a wider range of services and techniques. So, I created RIMPTM.
"Communication Protocol" - a set of guidelines or rules that establish a certain method of information transfer between two or more systems
Like HTTP, TCP was not designed specifically for rich media. Nor was it designed for today's wireless network.
Experts agree that TCP is ill equipped yet so highly implemented little can be done to modify the protocol. As a result, virtually every manufacturer of wireless devices, including phones, have created and adopted proprietary protocols. Most of these protocols intercept TCP and manage the actual connection - know as TCP accelerators. Certainly, some performance gains have been realized. However what is needed is a protocol based in part on TCP that could support a wider range of services and techniques. So I created JBTTM.
The RIMP/JBT/IP suite supports incoming and outgoing HTTP/TCP/IP connections working with existing TCP/UDP/IP configured networks as an accelerator. This means the networking and Internet applications do not require total reconfiguration, deployment and adoption of RIMP/JBT to function. When directly utilized by applications written to access RIMP/JBT, the full benefits are unleashed. Early ungoverned direct access trials have show performance increases as high as 20x on mobile devices. RIMP/JBT will be released in 2008 from Webby, Inc..
I developed the Rich Internet Media Protocol ("RIMP") as an application protocol replacement of HTTP, that could utilize JBT and several important capabilities I thought are very and yet completely missing from HTTP/HTTPS. RIMP can used in state or stateless communications unlike HTTP - that only operates as a stateless unidirectional communication system.
NOTE: Webby, Inc. is not yet online, check back later for updates.
