Explore chapters and articles related to this topic
XBee and Internet of Robotic Things Based Worker Safety in Construction Sites
Published in Vijender Kumar Solanki, Vicente García Díaz, J. Paulo Davim, Handbook of IoT and Big Data, 2019
Rajesh Singh, Anita Gehlot, Divyanshu Gupta, Geeta Rana, Ravindra Sharma, Shivani Agarwal
The representational state transfer (REST), or RESTful Web services, is the way to provide interoperability between computer systems that are connected to the Internet. Such types of Web services provide requests to the system to access and manipulate the textual representations of Web resources. The system uses the uniform and predefined set of stateless operations, which exposes the arbitrary sets of operations such as web service definition language (WSDL) and simple object access protocol (SOAP). The Web resources are already available in the World Wide Web (www) as documents or files identified by their URLs. The RESTful Web service and the resource URI then divide a response in XML, HTML, JSON, or some other defined format. The HTTP format uses the create, read, update and delete (CRUD) HTTP methods with commands GET, POST, PUT, DELETE, and so on.
Common Standards in Cloud Computing
Published in John W. Rittinghouse, James F. Ransome, Cloud Computing, 2017
John W. Rittinghouse, James F. Ransome
HTTP is a request/response communications standard based on a client/ server model. A client is the end user, the server is the web site. The client making a HTTP request via a web browser or other tool sends the request to the server. The responding server is called the origin server. HTTP is not constrained to use TCP/IP and its supporting layers, although this is its most popular application on the Internet. SIMPLE, the Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions, is an instant messaging (IM) and presence protocol suite based on Session Initiation Protocol, and it is managed by the IETF. Like XMPP, SIMPLE is an open standard. Extensible Messaging and Presence Protocol (XMPP) is also an open, XML-based protocol originally aimed at near-real-time, extensible instant messaging and presence information (e.g., buddy lists) but now expanded into the broader realm of message-oriented middleware. All of these protocols are discussed in detail in the following paragraphs.
Hypertext Transfer Protocol (HTTP)
Published in Hossam Fattah, LTE™ Cellular Narrowband Internet of Things (NB-IoT), 2021
Hyper Text Transfer Protocol (HTTP) is a protocol for World Wide Web (WWW) communication between web clients and servers. Communication between client computers and web servers is done by sending HTTP requests and receiving HTTP responses. Clients are often browsers (Chrome, Edge, Safari), but they can be any type of program or device. Servers can be in the cloud. HTTPS is the secure version of HTTP. HTTPS is encrypted in order to increase security of data transfer. Every time you visit a website starting with HTTPS, a public/private key encryption is being used. It is the basis of SSL and TLS encryption, which is employed for HTTPS communications. In this chapter, you will learn how to use HTTP and HTTPS using the NB board.
IoT-enabled cloud-based real-time remote ECG monitoring system
Published in Journal of Medical Engineering & Technology, 2021
Manju Lata Sahu, Mithilesh Atulkar, Mitul Kumar Ahirwal, Afsar Ahamad
The volume of the data generated by the ECG module is very high which necessitates the use of cloud computing platform. The storage of the data in cloud platform enables rapid storing of high-volume data in a very convenient way. Data storage in cloud platform also provides real-time analysis and remote monitoring of the patient. Implementation of the cloud-based storage for the proposed system is shown in Figure 6. The implemented system works on a conventional request–response method, where the HTTP server is able to receive the request from the client and respond accordingly. HTTP server provides only GUI of the ECG signal. Message Queuing Telemetry Transport (MQTT) protocol is used for the transmission of the ECG signal from ECG module to the application installed in smartphone acting as a mobile gateway. MQTT protocol maintains a long-lived connection between the device and the remote supervisor. It requires less communication overheads and helps to save bandwidth, because of these advantages; it is the most suitable server for providing real-time ECG data to the users.
An investigation on adaptive HTTP media streaming Quality-of-Experience (QoE) and agility using cloud media services
Published in International Journal of Computers and Applications, 2021
Selvaraj Kesavan, E. Saravana Kumar, Abhishek Kumar, K. Vengatesan
Web services helps to exchange information’s between applications in standard way using predefined principle. SOAP and REST interfaces are widely used to communicate between applications. SOAP communications causes network traffic, higher latency and processing delays. To overcome this limitations of SOAP, RESTful architecture is mostly adapted as favorable interfaces in web services. REST is a lightweight, easy and better alternative for the SOAP. REST support four main operations: create, read, update and delete. The REST operations are implemented using standard HTTP methods such as GET, PUT, POST, and DELETE for request and response operation. The REST messages consists of Universal resource identifier, header and message body. Since most of the available web services transforming towards to RESTful interfaces, we discuss more about enabling live and on demand adaptive http streaming media Services using RESTful interfaces. This section covers the general, required adaptive http streaming operation flow between application and media services. The operation flow and additional features varies between one to another cloud platform service providers. The adaptive HTTP streaming service in cloud platform available via standard interfaces and categorically divided into three phases namely (1) Media content upload/Live stream (2) Transcoding and adaptive content generation (3) content streaming to client players.
Application of the Internet of Things in the textile industry
Published in Textile Progress, 2019
Hitesh Manglani, George L. Hodge, William Oxenham
Using information available in the literature [39–42], application protocols are compared in Table 2. Each of the standards is divided into 4 categories: usage case; how it transports data; mechanism of data request and response; and finally, the mechanism to broadcast data. Prior to the comparison, it is helpful to appreciate HTTP REST, which has existed for a long time now and is quite well-established. The World Wide Web is based on the Hyper Text Transfer Protocol (HTTP). HTTP is a way to communicate data and file transfer. It is similar to hypertext documents, which include hyperlinks to other resources that the user can easily access. In a client-server model, HTTP functions as request-response protocol. For example, our web browsers are the client, and a computer hosting a website acts as a server. When a web browser submits an HTTP request to a server, the servers, in turn, respond with HTML files and other data.