WebRTC

3 results back to index

Mastering Ember.js by Mitchel Kelonye

Firefox, information security, MVC pattern, off-the-grid, Ruby on Rails, single page application, web application, WebRTC, WebSocket

In addition, these applications might also need to send data and receive updates to and from the server as quickly as possible. There are a number of web technologies that can be used to accomplish this need: Adobe Flash sockets JSONP polling XHR long polling XHR multipart streaming ActiveX HTMLFile Web sockets Server-sent events WebRTC In this chapter, we will learn how to use the Socket.io (http://socket.io) library, which enables bidirectional communication between web clients and servers. It does this by providing a similar API between the mechanisms just mentioned, excepting the last two. Additionally, it selects the best mechanism to use depending on a number of factors, such as browser support, among others.

…

Facebook newsfeeds and Twitter timelines are good examples of use cases that can benefit from this technology. The following resources can aid in the development of such an application: Sse client library available at https://github.com/segmentio/sse Sse Node.js library available at https://github.com/segmentio/sse-stream WebRTC is a good choice for applications that require peer-to-peer communication, such as audio and video streaming. Setting up Socket.io To aid in mastering Socket.io, we will explore the bundled chapter sample that is a simple IRC-style chat application and the backend of which is built in Node.js, as shown in the following screenshot: The only prerequisite is Node.js, which can be downloaded from http://nodejs.org/download.

The Tangled Web: A Guide to Securing Modern Web Applications by Michal Zalewski

barriers to entry, business process, defense in depth, easy for humans, difficult for computers, fault tolerance, finite state, Firefox, Google Chrome, information retrieval, information security, machine readable, Multics, RFC: Request For Comment, semantic web, Steve Jobs, telemarketer, Tragedy of the Commons, Turing test, Vannevar Bush, web application, WebRTC, WebSocket

The protocol is bootstrapped using a keyed challenge-response handshake, which looks sort of like HTTP and which is (quite remarkably) impossible to spoof by merely exploiting a header-splitting flaw in the destination site. Following a successful handshake, raw data may be exchanged bidirectionally within the resulting long-lived TCP connection, with each message enveloped inside a simple protocol frame. The mechanism is supported in WebKit and is probably coming soon to Firefox. P2P networking WebRTC[260] is a proposed set of APIs and network protocols designed to facilitate the discovery of and communication with other browsers without the need for a centralized server infrastructure. The primary use case for such a protocol is the implementation of IP telephony and video-conferencing features within web apps.

…

See World Wide Web, The Boring Period: 2000 to 2003 WebDAV, CONNECT WebGL, Plug-in-Based Application Frameworks, Plug-in-Based Application Frameworks WebKit parsing engine, Hypertext Markup Language, Inheritance for data: URLs, Inheritance for javascript: and vbscript: URLs, Character Set Inheritance and Override, CORS Request Types, Current Status of CORS, Content Security Policy, Strict Transport Security, XSS Filtering, URL- and Protocol-Level Proposals, Content-Level Features character set inheritance, Character Set Inheritance and Override CORS in, CORS Request Types, Current Status of CORS data: URLs in, Inheritance for data: URLs history.pushState() API, URL- and Protocol-Level Proposals Refresh redirection to javascript:, Inheritance for javascript: and vbscript: URLs Strict Transport Security support, Strict Transport Security Worker API, Content-Level Features XSS-detection logic, XSS Filtering WebRTC, URL- and Protocol-Level Proposals WebSocket API, URL- and Protocol-Level Proposals WebSQL API, Content-Level Features Western European code page (ISO-8859-1), Header Character Set and Encoding Schemes WHATWG (Web Hypertext Application Technology Working Group), Web 2.0 and the Second Browser Wars: 2004 and Beyond whitelists, Browser- and Plug-in-Managed Site Permissions whitespace, Understanding HTML Parser Behavior, Character Encoding window handles, Changing the Location of Existing Documents window splicing, Window-Positioning and Appearance Problems window.alert() API, Pop-Up Filtering window.blur() function, Connection Limits, Window-Positioning and Appearance Problems window.confirm() API, Pop-Up Filtering window.createPopup() API, Window-Positioning and Appearance Problems window.focus() method, Window-Positioning and Appearance Problems window.moveTo() method, Window-Positioning and Appearance Problems window.name property, of frames, Changing the Location of Existing Documents window.notifications API, Content-Level Features window.open() function, The Document Object Model, Life Outside Same-Origin Rules, Connection Limits, Connection Limits, Dialog Use Restrictions, Window-Positioning and Appearance Problems window.print() API, Pop-Up Filtering window.prompt() API, Pop-Up Filtering window.resizeTo() method, Window-Positioning and Appearance Problems window.showModalDialog() API, Connection Limits windows, Life Outside Same-Origin Rules, Changing the Location of Existing Documents, Changing the Location of Existing Documents, Connection Limits, Dialog Use Restrictions and frame interactions, Life Outside Same-Origin Rules anonymous, Changing the Location of Existing Documents creating new in browser, Connection Limits positioning, Dialog Use Restrictions Windows Media Player, Audio and Video, Document Rendering Helpers, Adobe Flash Windows operating system, The First Browser Wars: 1995 to 1999, Web 2.0 and the Second Browser Wars: 2004 and Beyond Windows Presentation Foundation, Microsoft Silverlight, XML Browser Applications (XBAP) Wireless Application Protocol suite (WAP), Wireless Markup Language Wireless Markup Language (WML), Wireless Markup Language WMF file format, Type-Specific Content Inclusion WML (Wireless Markup Language), XML User Interface Language WML Script (WMLS), and JavaScript, XML User Interface Language Worker API, Content-Level Features World Wide Web, A Brief History of the Web, Tales of the Stone Age: 1945 to 1994, The First Browser Wars: 1995 to 1999, Document Rendering Helpers, A Glimpse of Things to Come, A Glimpse of Things to Come browser wars, The First Browser Wars: 1995 to 1999, A Glimpse of Things to Come history, A Brief History of the Web threat of hostile takeover, Document Rendering Helpers World Wide Web Consortium (W3C), The First Browser Wars: 1995 to 1999, The Boring Period: 2000 to 2003, Hypertext Markup Language, Current Status of CORS creation of, The First Browser Wars: 1995 to 1999 Microsoft and, Current Status of CORS worms, The Boring Period: 2000 to 2003 WWW-Authenticate header, HTTP Cookie Semantics, HTTP Authentication wyciwyg: scheme, Protocols Claimed by Third-Party Applications and Plug-ins X X-Content-Type-Options header, Character Set Handling X-Content-Type-Options: nosniff header, Unrecognized Content Type X-Frame-Options header, Unsolicited Framing, Primary CSP Directives XAML (Extensible Application Markup Language), Properties of ActionScript Xanadu, Tales of the Stone Age: 1945 to 1994 XBAP (XML browser applications), Sun Java XBL bindings, Basic CSS Syntax XDomainRequest API, Current Status of CORS, XSS Filtering XHTML, The Boring Period: 2000 to 2003, Hypertext Markup Language, The Battle over Semantics, Entity Encoding, Entity Encoding and HTML entities, Entity Encoding minimal fault-tolerance of parser, The Battle over Semantics named entities, Entity Encoding syntax, Hypertext Markup Language XML (Extensible Markup Language), Document Parsing Modes, Document Parsing Modes, Entity Encoding, XML User Interface Language, XML User Interface Language, Wireless Markup Language, Other Developments <!

Industry 4.0: The Industrial Internet of Things by Alasdair Gilchrist

3D printing, additive manufacturing, air gap, AlphaGo, Amazon Web Services, augmented reality, autonomous vehicles, barriers to entry, business intelligence, business logic, business process, chief data officer, cloud computing, connected car, cyber-physical system, data science, deep learning, DeepMind, deindustrialization, DevOps, digital twin, fault tolerance, fulfillment center, global value chain, Google Glasses, hiring and firing, industrial robot, inflight wifi, Infrastructure as a Service, Internet of things, inventory management, job automation, low cost airline, low skilled workers, microservices, millennium bug, OSI model, pattern recognition, peer-to-peer, platform as a service, pre–internet, race to the bottom, RFID, Salesforce, Skype, smart cities, smart grid, smart meter, smart transportation, software as a service, stealth mode startup, supply-chain management, The future is already here, trade route, undersea cable, vertical integration, warehouse robotics, web application, WebRTC, Y2K

Before mainstream digitization, back in the 2000s, companies could be contacted by telephone or e-mail. Today, companies have click to chat or call to communicate with a live support agent on their web sites, or they have online forms to open service tickets on their sites for customers’ convenience. Other technologies are gaining acceptance, such as video calls using WebRTC, which enables a customer to contact a support center via a browser using video chat. This is proving important when technical support agents need to actually see the product and can make fault diagnosis and fault resolution much quicker. Similarly, the massive growth in mobile apps has led companies to produce their own apps, which further integrates the customer with the company and provides even more intelligence such as location.