WebSocket Connection Research Articles

Diesel Level Monitoring System

Abstract: The ultimate objective of this project is to create a wireless diesel tank monitoring system that employs WebSocket protocol to connect fuel sensors and a mobile app in remote areas in real time. Through the use of Wi-Fi networks, customers can obtain consumption information, monitor the current diesel levels in various tanks, and log in to the mobile app, which has a straightforward interface. Diesel levels are shown as a percentage, translated from voltage readings, and alerts are delivered by the system when levels drop below preset limits. The goal of this effective and user-friendly technology is to maximize the use of diesel and make timely refills in distant places easier. A reliable and smooth solution for diesel level monitoring is made possible by the integration of the ESP32 microcontroller, WebSocket connection, and capacitive fuel level sensor. Accurate mapping of sensor readings to ESP32 values is made possible by the use of a 20k ohm potentiometer, which guarantees accurate and dependable data transfer. This work advances the area of remote monitoring systems by providing a workable and expandable method for monitoring diesel level in a variety of applications.

Comparison of WebSocket and Hypertext Transfer Protocol for Transfer of Electronic Health Records.

Electronic health records (EHR) emerged as a digital record of the data that is generated in the healthcare. In this paper the transfer times of EHRs using the Hypertext Transfer Protocol and WebSocket in both local network and wide area network (WAN) are compared. A python web application to serve Fast Health Interoperability Resources (FHIR) records is created and the transfer times of the EHRs over both HTTP and WebSocket connection are measured. 45000 test Patient resources in 20, 50, 100 and 200 resources per Bundle transfers are used. WebSocket showed much better transfer times of large amount of data. These were 18 s shorter in the local network and 342 s shorter in WAN for the 20 resource per Bundle transfer. RESTful APIs are a convenient way to implement EHR servers; on the other hand, HTTP becomes a bottleneck when transferring large amount of data. WebSocket shows better transfer times and thus its superiority in such situations. The problem can be addressed by developing a new communication protocol or by using network tunneling to handle large data transfer of EHRs.

CERVI: collaborative editing of raster and vector images

Various web-based image-editing tools and web-based collaborative tools exist in isolation. Research focusing to bridge the gap between these two domains is sparse. We respond to the above and develop prototype groupware for real-time collaborative editing of raster and vector images in a web browser. To better understand the requirements, we conduct a preliminary user study and establish communication and synchronization as key elements. The existing groupware for text documents or presentations handles the above through well-established techniques. However, those cannot be extended as it is for raster or vector graphics manipulation. To this end, we develop a document model that is maintained by a server and is delivered and synchronized to multiple clients. Our prototypical implementation is based on a scalable client–server architecture: using WebGL for interactive browser-based rendering and WebSocket connections to maintain synchronization. We evaluate our work qualitatively through a post-deployment user study for three different scenarios. For quantitative evaluation, we perform a thorough performance measure on both client and server side, thereby identifying design recommendations for future concurrent image-editing software(s).

Poor Coding Leads to DoS Attack and Security Issues in Web Applications for Sensors

As the SQL injection attack is still at the top of the list at Open Web Application Security Project (OWASP) for more than one decade, this type of attack created too many types of issues for a web application, sensors, or any similar type of applications, such as leakage of user private data and organization intellectual property, or may cause Distributed Denial of Service (DDoS) attacks. This paper focused on the poor coding or invalidated input field which is a big cause of services unavailability for web applications. Secondly, it focused on the selection of program created issues for the WebSocket connections between sensors and the webserver. The number of users is growing to use web applications and mobile apps. These web applications or mobile apps are used for different purposes such as tracking vehicles, banking services, online stores for shopping, taxi booking, logistics, education, monitoring user activities, collecting data, or sending any instructions to sensors, and social websites. Web applications are easy to develop with less time and at a low cost. Due to that, business community or individual service provider’s first choice is to have a website and mobile app. So everyone is trying to provide 24/7 services to its users without any downtime. But there are some critical issues of web application design and development. These problems are leading to too many security loopholes for web servers, web applications, and its user’s privacy. Because of poor coding and validation of input fields, these web applications are vulnerable to SQL Injection and other security problems. Instead of using the latest third-party frameworks, language for website development, and version database server, another factor to disturb the services of a web server may be the socket programming for sensors at the production level. These sensors are installed in vehicles to track or use them for booking mobile apps.

Elastic Akka Cluster with Websockets

In this paper we will discuss an automated cost-effective solution to induce elasticity in a system dealing with the persistence of websocket connection. We are going to make use of the concept of Akka Clustering to ensure there is no single point of failure making the system resilient. The system is deployed using automation to the AWS cloud where we will make use of Cloudwatch and Lambda functions to scale up or down the cluster as traditional methods to scaling based on memory and CPU utilization will not suffice. The elastic nature of the system will make it flexible to deal with variable loads in terms of connected clients and scale based on the number of connected clients. The use of AWS auto-scaling will also ensure the system is highly available.

WoT Communication Protocol Security and Privacy Issues

In this paper, we have proposed a novel approach for the prevention of the Internet of Things (IoT) from fake devices and highlighted privacy issues by using third party Application Program Interface (RestAPI) in Web of Things (WoT). For the ease of life, the usage of IoT devices, sensors, and Radio-Frequency Identifications (RFIDs) increased rapidly. Such as in transport for monitoring vehicles, taxi services, healthcare for patient’s health condition monitoring, smart cars, smart grids, and smart homes, etc. Due to this for financial gain attackers are targeting these networks or protocol and adversaries are trying to damage the reputation of the organization or to steal intellectual property. From the last two decades or more, the injection vulnerabilities are more threatening security risks for the web application still exists. The new security challenges occur for the security professional or security researchers in the form of IoT or WoT (Web of Things) communication protocols implementation. These protocol Message Queuing Telemetry Transport (MQTT), Constrained Application Protocol (CoAP), WebSockets, and RestAPI have a different type of security issues. Respectively insertion of fake devices, authentication is not implemented in WebSocket connections, and user’s privacy can be leaked with the use of RestAPI without its validation. We have developed a program in Personal Home Pages (PHP) for the detection of new devices in the IoT network. With this, the user’s privacy and data will be protected along with some critical security issues of WoT underlying protocols.

Multiparty Session Type-safe Web Development with Static Linearity

Modern web applications can now offer desktop-like experiences from within the browser, thanks to technologies such as WebSockets, which enable low-latency duplex communication between the browser and the server. While these advances are great for the user experience, they represent a new responsibility for web developers who now need to manage and verify the correctness of more complex and potentially stateful interactions in their application. In this paper, we present a technique for developing interactive web applications that are statically guaranteed to communicate following a given protocol. First, the global interaction protocol is described in the Scribble protocol language -- based on multiparty session types. Scribble protocols are checked for well-formedness, and then each role is projected to a Finite State Machine representing the structure of communication from the perspective of the role. We use source code generation and a novel type-level encoding of FSMs using multi-parameter type classes to leverage the type system of the target language and guarantee only programs that communicate following the protocol will type check. Our work targets PureScript -- a functional language that compiles to JavaScript -- which crucially has an expressive enough type system to provide static linearity guarantees. We demonstrate the effectiveness of our approach through a web-based Battleship game where communication is performed through WebSocket connections.

Pulse oximeter with Internet data visualization

In this work, we describe the design and construction of a pulse oximeter for remote patient monitoring. The proposed device uses the ESP8266 microcontroller as the core component to establish the wireless connection and send information to a node.js server. Then, a web service shows the saturation of oxygen and the heart rate through a WebSocket connection. This paper describes the hardware and software designs, justifying the decision to select each component of the proposed device. Finally, some experimental results are shown to illustrate the performance of the developed prototype.

Querying a graph database – language selection and performance considerations

NoSQL and especially graph databases are constantly gaining popularity among developers as they promise to deliver superior performance when handling highly interconnected data compared to relational databases. Apache Shindig is the reference implementation for OpenSocial with a highly interconnected data model. However, it had a relational database as back-end. In this paper we describe our experiences with the graph database Neo4j as back-end and compare Cypher, Gremlin and Java as alternatives for querying data with MySQL. We consider performance as well as usability from a developer's perspective. Our results show that Cypher is a good query language in terms of code readability and has a moderate overhead for most queries (20–200%). However, it has to be supplemented with “stored procedures” to make up for some performance deficits in pattern matching queries (>1000%). The RESTful API is unusable slow, whereas our WebSocket connection performs significantly better (>650%).

An Architecture to use Easy Java-Javascript Simulations in New Devices

Nowadays, virtual and remote laboratories play an important role in the students’ learning process. For distance education in scientific areas, where the laboratories are an essential part, this importance is especially relevant. In the last years, the newly discovered Java vulnerabilities and the new devices which do not support Java applications (tablets and smart-phones), make even harder to run or develop these laboratories as Java applications. On the one hand, a non-digitally signed applet cannot be run in a web browser or in a smart-phone. On the other hand, portable devices, like a pc-tablet, have limited computation resources, and sometimes it is not enough to run complex simulations. EjsS (Easy Java-Javascript Simulations) is an open source tool used for creating all kind of simulations by introducing the equations of the model, and building a graphical user interface (GUI) for the application. This work presents a solution to the two previous problems that appear when using EjsS. Both are resolved using a Java model that runs in a server and takes the heavier computational load. This Java model is linked with a Javascript GUI in the client device. The link is based on a web-socket connection between server and client using a JSON format. The proposed solution has additional advantages, such as the possibility of multiple users working with the same model, or reusing an already existing Java application by just building a new Javascript view.

An Empirical study of HTML5 Websockets and their Cross Browser behavior for Mixed Content and Untrusted Certificates

allow a full duplex connection to be made over a single socket between the client and the server. Today, Websockets is a finished standard and has greatly helped modern web applications to achieve real time communication without any overhead of sending HTTP headers with every request. This research provides an overview of the Websocket protocol and API, and focuses on the state of Websocket security. The research also aims to explicate behavior of different browser implementations of Websockets when delivering mixed content (ws/https) and the browser response when an untrusted certificate is encountered while making a secure Websocket connection. The crux of this paper is to analyze at the grassroots security concerns pertaining to Websockets and discuss best practices for secure deployment. KeywordsHTTP, Mixed Content, Security, Websockets.

Communicating and Displaying Real-Time Data with WebSocket

Internet communication provides a convenient, hyperlinked, stateless exchange of information, but can be problematic when real-time data exchange is needed. The WebSocket protocol reduces Internet communication overhead and provides efficient, stateful communication between Web servers and clients. To determine whether WebSocket communication is faster than HTTP polling, the authors built a Web application to measure the one-way transmission latency of sending real-time wind sensor data at a rate of 4 Hz. They implemented a Jetty servlet to upgrade an HTTP connection to a WebSocket connection. Here, they compare the WebSocket protocol latency to HTTP polling and long polling.