3 results back to index
Mastering Ember.js by Mitchel Kelonye
However, today's modern applications strive to offer the best user experience through reduced page reloads, efficient data transfers, and improved performances. 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. Before diving into using Socket.io, it's worth noting that server-sent events are a good option if the client app is meant to constantly receive updates from the backend while performing little or no pushes.
Before diving into using Socket.io, it's worth noting that server-sent events are a good option if the client app is meant to constantly receive updates from the backend while performing little or no pushes. 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, RFC: Request For Comment, semantic web, Steve Jobs, telemarketer, 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 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. No stable browser support is available yet. Offline applications Cache manifests are a relatively simple way for a web server to instruct the browser that copies of certain documents should be stored indefinitely and reused whenever the client appears to have no network connectivity.
Industry 4.0: The Industrial Internet of Things by Alasdair Gilchrist
3D printing, additive manufacturing, Amazon Web Services, augmented reality, autonomous vehicles, barriers to entry, business intelligence, business process, chief data officer, cloud computing, connected car, cyber-physical system, deindustrialization, fault tolerance, global value chain, Google Glasses, hiring and firing, industrial robot, inflight wifi, Infrastructure as a Service, Internet of things, inventory management, job automation, low skilled workers, millennium bug, pattern recognition, peer-to-peer, platform as a service, pre–internet, race to the bottom, RFID, Skype, smart cities, smart grid, smart meter, smart transportation, software as a service, stealth mode startup, supply-chain management, trade route, web application, WebRTC, WebSocket, Y2K
Industry 4.0 Customer Contact Points One of the major digital contributions to the business is by the increase of customer contact points. 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.