Mee-ng in San Jose, California: – Discussion about the rise of web applica-ons – Vote on upda-ng HTML for web applica-ons: ü 8 For ü 14 Against • Result: – Web Hypertext Applica*on Technology Working Group (WHATWG) formed 2 days later – Web Applica*ons 1.0 à HTML5
– h]p://www.w3.org/TR/cors/ – h]p://enable-‐cors.org • Allows (safe) exemp-ons from the Same-‐Origin Policy – “With CORS you receive data instead of [JSONP] code, which you can parse safely” —Frank Salim
data from server to browser • EventSource API • Great for newsfeeds, one-‐way streams of data • SSE-‐specific features: ü Automa-c reconnec-on ü Event IDs
RFC 6455) • Allows browser to communicate with a remote host • Full-‐duplex (bi-‐direc-onal), single socket • Port 80/443 (ws:// and wss://) • Huge reduc-on in unnecessary overhead and latency • A socket in your browser!
you can extend client-‐server protocols to the web: ü Chat: XMPP (Jabber), IRC ü Pub/Sub (Stomp/AMQP) ü VNC (RFB) ü Any TCP-‐based protocol • The browser becomes a first-‐class network ci-zen • Demo: This presenta-on in real -me! h]p://demo.kaazing.com/presso
to TLS/port 443 – Encrypted tunnel allows traversal of intermediaries – Less overhead than originally thought – Example: SPDY • Using standard, open ports has a big advantage "We want some chance of geCng this (SPDY) protocol out in our live Hme” —Roberto Peon (Google) • And more: – Single Sign-‐On, Authen-ca-on and Authoriza-on For example, Kaazing Kerberos protocol over WS
Real Time Presenta-on: h]p://www.slideshare.net/peterlubbers/html5-‐real-me-‐and-‐ connec-vity • HTML5 Weekly Newsle]er: h]p://html5weekly.com/ • The Web Ahead Podcast: h]p://5by5.tv/webahead/ • San Francisco HTML5 User Group (monthly presenta-ons and videos): h]p://sutml5.org • Kaazing WebSocket Gateway: h]p://kaazing.com/
training worldwide (experts, not just trainers) • Customers include Google, Cisco, Intel, and more • Web site: h]p://kaazing.com/training/ • E-‐mail us: [email protected]