The Web That is Instantly On, and Always On

Kaazing Journal

Subscribe to Kaazing Journal: eMailAlertsEmail Alerts newslettersWeekly Newsletters
Get Kaazing Journal: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Kaazing Authors: Jason Bloomberg, Kaazing Blog, Jnan Dash, Jeremy Geelan, Stacy Gorkoff

Related Topics: Kaazing Journal, CIO/CTO Update, WebRTC Journal

Blog Feed Post

Real Time Data Panel Discussion at Edge Conference 2013

At the Edge Conference in New York City last week a panel of 5 industry experts discussed some of the exciting questions and challenges of real time data. Here’s the abstract of the discussion:

WebSockets have now been with us for several years and enjoy near universal support. WebRTC is just starting out. Chat, live blogging, telemetry/dashboards, remote assist and video conferencing are all proven and popular use cases for real time data. Developers are becoming increasingly comfortable integrating real time elements into new projects, but problems remain with the complexity of scaling a real-time backend, as well as implementing APIs that are practical and useful.

john-fallowsBesides John Fallows, CTO and co-founder of Kaazing, Henrik Joreteg (&yet), Martyn Loughran (Pusher), Wesley Hales (Apigee), and Rob Hawkes (ViziCities) were invited to be on the panel, moderated by Scott Jenson (Jenson Design).

Here are a few deep links into interesting questions and topics addressed during the panel:

Question (14:26): WebSocket and other real-time protocols are commonly blocked by corporate proxies and content inspection firewalls; and that’s a particular problem for the sort of customers we have at the FT. How much is this stifling adoption and what do we do about it?

Question (22:42): Will the WebSocket protocol replace Server-Sent Events in the future? Why do we have to have both specs if WebSocket can accomplish the same tasks that SSE does, and more?

Question (35:30): We see a rise of security issues; people are trying to open too many TCP connections to a Web server and are killing the Web server as a result of it. Therefore, people tend to disable keep-alive connections to deal with this issue. What do you think about WebSocket security related to this problem and how can we solve it?

John on enabling the Web of Things (49:21)


Read the original blog entry...

More Stories By Kaazing Blog

Kaazing is helping define the future of the event-driven enterprise by accelerating the Web for the Internet of Things.