Channels ▼
RSS

Web Development

Kaazing WebSocket Gateway Pushes Offline iPhone Data


Kaazing has announced its WebSocket Gateway — JMS Edition 3.5 Platform. Built around the firm's HTML 5 web socket architecture, the new platform sets out to improve iPhone battery life, application performance, and "offline participation" so that apps can push information to devices even when they're not "on".

The firm claims to be able to provide iPhone app developers with cost savings and a lower maintenance burden. Kaazing CEO Jonas Jacobi argues that most iPhone apps rely on using HTTP as "the earliest architecture of the Internet".

"HTTP wasn't designed for the real-time responsiveness you need for apps dealing with air travel, finances, gaming, transportation, or online collaboration," said Jacobi. "Building a live, interactive, and real-time application using Kaazing's HTML5 WebSocket technology requires less power and less data, meaning longer battery life in mobile devices, more responsive applications, and less impact on end users data plans."

The company's own data states that Kaazing Gateway has been shown to be at least “50% more efficient” than traditional web communications (like HTTP) for mobile app performance. Although no third party independent clarification or verification of this figure was provided, Kaazing does also state that it is able to reduce latency to give apps a more responsive feel.

"The full-duplex nature of Kaazing's solution means true real-time mobile applications rather than the pseudo-real-time applications that eat up bandwidth and drain batteries," said the company.

Key features of the Kaazing WebSocket Gateway – JMS Edition 3.5 Platform include an iOS client library for writing native iPhone applications, APNS Integration to reach an audience even when they are not logged into a native application, client-managed message flow control to ensure continued service through poor coverage areas, and bandwidth capping to offer volume-tiered data delivery services.


Related Reading


More Insights






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 
Dr. Dobb's TV