RU2813837C2 - Graphical object management system - Google Patents

Abstract

FIELD: computer engineering.

SUBSTANCE: invention relates to web application management systems. Technical result is achieved due to configuration of client part containing local canvas Canvas. Local canvas Canvas is configured to load the web browser of a standard html document from the server side containing the client code. Client code contains a command to draw an object on the local canvas Canvas of the client side.

EFFECT: high efficiency and security of data on a server.

6 cl, 4 dwg

Description

The present invention relates to computer technology, in particular to systems for managing web applications provided over a data network such as the Internet, and can be used to manage developer graphical interface application objects and their user-server interactions.

Definitions, abbreviations and acronyms

To simplify and reduce the cost of information processing, as well as to store it, a type of computer technology is currently used - servers. The user (client) wanting to access the server is located in a different location. A computer network is used to transfer data between the client and server. This can be either a local computer network of an enterprise or the Internet.

The following definitions are used in this description.

Data transmission (data exchange, digital transmission, digital communication) is the physical transfer of data (digital bit stream) in the form of signals from point to point or from point to several points, usually for subsequent processing by computer technology.

Data transmission network - a set of three or more terminal devices (terminals) of communication, united by data transmission channels and switching devices (network nodes) that ensure the exchange of messages between all terminal devices.

Computer network, computer network - a system that provides data exchange between computing devices - computers, servers, routers and other equipment or software. Various data transmission media can be used to transmit information.

Local area network (LAN) is a computer network that usually covers a relatively small area or a small group of buildings (home, office, company, institute).

The Internet is an information and communication network and a worldwide system of interconnected computer networks for storing and transmitting information.

The OSI network model (The Open Systems Interconnection model) is a network model of the OSI/ISO network protocol stack (store). Through this model, various network devices can communicate with each other. The model defines different levels of interaction between systems. Each level performs specific functions in such interaction.

WebSocket is a communication protocol over a TCP connection designed to exchange messages between a browser and a web server in real time.

TCP connections (Transmission Control Protocol) are one of the main Internet data transfer protocols. Designed to manage Internet data transfer. Packets in TCP are called segments. In the TCP/IP protocol stack, it performs the functions of the transport layer of the OSI model.

Computing is technology used for calculations. Computer technology is a critical component of the computing and data processing process. Includes hardware and software, also used for managing and processing information.

API (Application Programming Interface) is a description of the ways (a set of classes, procedures, functions, structures or constants) in which one computer program can interact with another program.

Graphical user interface (GUI - graphical user interface) is a system of tools for user interaction with electronic devices, based on the presentation of all system objects and functions available to the user in the form of graphical screen components. Includes interactive elements: window manager, buttons, input fields, drop-down lists and others that allow the user to interact using input devices (keyboard, mouse, etc.) with the program (application, because the program uses OS functions rather than implementing these elements itself)

User interface (UI - user interface) is an interface that ensures the transfer of information between a human user and the hardware and software components of a computer system.

The client - or the client link, the client part - is the user's terminal, in most cases remote, connected to the server.

A user is a person or organization that uses an operating system to perform a specific function.

Server - or server part - a computer device or a set of devices designed for processing and storing information, executing commands coming from several personal computer devices located remotely.

Application - an application program designed to perform specific tasks and designed to interact with the user. In most operating systems (OS), application programs cannot access computer resources directly, but interact with hardware and other programs through the OS.

Canvas is an element of the HTML5 standard intended for creating a raster two-dimensional image: contours and filling the contour with color, straight lines, points, Bezier curves, text output (character contours in modern fonts are described by Bezier curves) using scripts

An event is an action performed by a user in an application.

A critical event is an event that must be sent immediately to the server in order to synchronize the states of the client and server (as opposed to an event that may be sent with a time delay).

A unique event is an event that is ultimately sent to the server.

Cumulative events are client-side events that are stored in the event queue until a critical event occurs. Then, when a critical event occurs, the client forwards the entire queue of events that occurred between the previous critical event and the current critical event

A control is a displayed application component (for example, a button, a field, etc.). Each control can perform specific operations (for example, receiving keyboard input, pressing, etc.

Main Form Window: The first window that the user sees when accessing a URL that is being processed using this technology. This window is equivalent to the main window that opens when you launch a desktop application.

Container: a window that contains controls

Update commands: A set of XML (Extensible Markup Language) elements that the browser executes to keep itself in sync with the application's object tree and server control state.

Window structure: A set of XML elements that describe the structure of the current application window. The window structure is used to update the state of the client link (the currently drawn UI) in accordance with the state of the server link (the current state of the UI on the server).

XML-based data: XML data that is used by the client to store application interface state. The application's interface state contains the properties of each UI control and includes all the information the client needs to synchronize the state of its controls with the server's state, such as the control's color or size, the text it displays, and so on. This provides the client end with the ability to redesign any part of the UI by using XSLT (template transformation) on XML-based data.

Currently, two main systems are used to provide client access to server resources: WEB and RDP.

WEB - access to a web server via hypertext technology. Hypertext documents hosted either on the World Wide Web or on an enterprise server in a closed network (with or without limited external access) are called web pages. Multiple web pages that share a common theme or design, and are linked by links, usually residing on the same web server, are called a website. To download and view web pages, special programs are used - browsers.

RDP ( Remote Desktop Protocol ) is an application-level protocol used to ensure remote user work with a server running a terminal connection service. Clients exist for almost all versions of Windows, Linux, FreeBSD, Mac OS X, iOS, Android, Symbian.

DLP system is software designed to protect a company from information leaks. From English Data Loss Prevention or Data Leakage Prevention. Most often, this abbreviation is used for products of this class.

State of the art

A technical solution is known according to patent RU No. 2420797 C2, G06F 15/16 (2006.01), G06F 9/44 (2006.01), publ . 06/10/2011, PCT application: US 2006/017568 (05/05/2006), according to which PROVIDING THE POSSIBILITY OF APPLYING THE GRAPHICS WINDOW CHANGE COMMAND TO A REMOTELY GENERATED GRAPHICS WINDOW performs a modification of a remotely generated graphical application window, in which a graphical application window is generated on first car. Next, a representation of the application's graphical window is sent to the second machine. A user command from the second machine to change the view is then detected. Then the user command is transmitted from the second machine to the first machine. In this case, it is determined whether the application's graphical window is in the mode of displaying the entire contents of the window or the outline mode. In display-all-content mode, windows periodically update the entire graphical application window during modification. Outline mode periodically updates a line indicating the new position and size of the application's graphics window during modification.

The known technical solution has disadvantages.

Firstly, patent RU 2420797 C2 describes part of the functionality of Microsoft's server product line of the Windows operating system, and therefore cannot be used as a separate program on Linux OS. Our development assumes use on any OS that supports modern browsers.

The advantage of the proposed technical solution: the proposed system will work under any OS for which a modern browser is developed.

Secondly, the analogue of RU 2420797 C2 generates a raster image of windows on the server using the functions of the graphics core of the Windows OS. The inventive system does not require the presence of a graphics core of the OS and does not generate a bitmap of windows on the server; the server part creates a bitmap of a window on the client by calling commands from the client's graphical interface. Which gives the following advantages:

- the amount of server memory used is significantly reduced, because memory allocation for storing the window bitmap image is not required.

- the consumption of computing power of the server processor is reduced, because the line drawing command is executed on the client, the server does not wait for a response from the client with the result of executing this function and sends the next command in the queue.

Thirdly, the patent RU 2420797 C2 does not include the ability to transfer windows between user sessions. In the inventive system, windows, or parts thereof, can be transferred or shared by clients. At the same time, an advantage is realized: the functionality of working with applications is expanded, because It is possible to collaborate with the application or part of it, with a limited or unlimited number of users, as well as to demonstrate it.

Fourthly, the patent RU 2420797 C2 assumes the use of a special client program installed on the client OS. The proposed system uses a web browser supporting HTML5 technology as a client. Which once again confirms the advantage of the proposed system, which will work under any OS for which a modern browser is developed.

Let's consider well-known systems designed for input/output and access to information, starting from a personal computer.

One case: The system of operation of a single-user application on a personal computer - The architecture of a personal computing device is a system for interaction (control) of the levels of a personal computing device.

This is a system with the possibility of one-way communication (request - response) from input devices to the application level and then to the user interface, with subsequent access to the canvas (Canvas).

In addition to this, there are the following client-server application systems.

For example, another case: WEB architecture - a system of interaction between a user and a server using a WEB browser. Communication is unidirectional - request only from the user, response from the server.

In this case, the user, through input devices, contacts the WEB browser of the user device, from which a request is made to the user interface, and then to the canvas, while the WEB browser, through its network interface, sends a request to the server through the server’s network interface, the request is processed at the application level server and sends a response via the network interface to the user.

The differences in the development systems for web applications and regular applications are that to write a web application you need to install and configure a web server, use the HTML language, or the JavaScript programming language, or any other language to write a module that integrates with the web server , know the formats of data transfer between client and server.

Disadvantages of known widely used systems:

- one-way client-server communication.

- use of single-threaded JavaScript language.

- use of different programming languages for the client and server parts.

- discrepancies in the display of the same page by different browsers.

- confusing logic of interaction between client and server (usually different teams of frontend and backend developers).

- use of third-party software (sometimes without documentation and from an unknown source).

- problems with security and fault tolerance (third-party software cannot be changed, even if the error is known).

- difficulty debugging the application.

Another example of a user-server interaction system.

The RDP architecture from MS, in which a system is built with the possibility of bidirectional communication (requests and responses in both directions). Events from input devices are received by the browser, but with the ability to be broadcast and processed on the server. Object rendering commands are executed on the server, which entails resource consumption.

The system contains user devices and a server, with the ability for the user to contact the server through input devices and an RDP client through the network interface of the user and server sequentially to the server application level, which, through the user interface, forms a user canvas from which the picture (image) is transferred to the local canvas user.

The well-known system has a number of advantages over WEB, such as:

1. Possibility of bidirectional communication (requests and responses in both directions).

2. Events from input devices are received by the client, but with the ability to be translated and processed on the server.

At the same time, there are significant disadvantages:

1. What is transferred from the server to the client is not a description of the object and actions with it, but pictures (images).

2. Commands for drawing objects are executed on the server in the GUI, which entails the consumption of resources.

3. Not a standard browser was used, but an RDP client application.

Clients (client part) can be:

1. Written by the developer for popular operating systems and thus avoid browser limitations. The complexity is obvious - you need to develop a client application for all popular operating systems and create your own update center.

2. You can use universal clients for desktop access technology, but then the server must contain a graphics subsystem, which will put a high load on the server operating system: the application will use the OS graphics subsystem to generate a bitmap and transfer it to the client.

3. You can use your web browser as a universal client. But this is not always possible due to the limitations stated at the beginning.

The closest analogue is the technical solution according to the patent US 2012/0151372 A1, G06F 3/01, dated 06/14/2012, METHODS AND SYSTEMS FOR FACILITATINGA REMOTE DESKTOP SESSION UTILIZINGA REMOTE DESKTOP CLIENT COMMON INTERFACE for which the description provides “examples of methods, systems , devices and machine-readable media to facilitate access and control of the remote desktop of a remote machine using a web browser on the client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. The transcoding server can convert user input requests from a web browser into input calls compatible with the Remote Desktop Display Protocol. The transcoding server can receive remote desktop drawing commands from the remote computer and convert the remote desktop drawing commands into web browser drawing updates compatible with the web browser. The transcoding server can communicate with a web browser via HTTP and communicate with a remote computer via the Remote Desktop Display Protocol. The web browser may be an HTML5 browser. The transcoding server can send drawing coordinates to the web browser via an HTTP header and can use long polling.

The common features of the analog and the proposed technical solution are the presence of a server and client parts, the configuration of the server part with the ability to provide an API to third-party programs running on the server, with the ability to implement standard HTTPS WebSocket Secure network protocols for connecting client browsers.

However, there are design differences in the content of the server and client parts of the compared technical solutions. The claimed invention differs from the analogue of patent No. US 2012/0151372 A1 in the location of Canvas - in the claimed system it is located on the client side. While in well-known graphical environments, including the analogue system (patent No. US 2012/0151372 A1) - on the server. This essential feature entails, as a consequence, a difference in the possibilities of generating and transmitting a raster image to the Client. The disadvantage of the analogue is the high computational load, which falls entirely on the Server, and only the result is transferred to the Client, as a result of which the analogue has insufficient performance of interaction between the user and the server, insufficient data security on the server, and high consumption of user device resources.

The above disadvantages are eliminated by the proposed technical solution, as a result of which the computational load for generating the final image is optimally distributed between the Client and the Server, making it possible to increase the performance of interaction between the user and the server, increase the security of data on the server, and reduce the consumption of user device resources.

At the same time, we unload the server from drawing functions, because Canvas is brought to the client, which saves processor resources and memory allocated for virtual buffers. We also speed up the operation of applications - for example, an application, having called a client function to draw text, does not wait for execution to complete (control of command delivery from the server to the client occurs at the network level)

To solve these problems, it is proposed to transform the system for providing and exchanging information at the application (upper) level of the OSI model, transmitted through any computer network (LAN, Internet).

The proposed solution is to partially transfer the functions of the graphics system to the server side (specifically, GUI/UI). To do this, we will use the Canvas object to capture events from input devices.

To solve the one-way direction of request initiation, we will use the new WebSocket transport protocol. Both objects are described in the HTML5 standard and are supported by all modern browsers.

All data exchange between the client and the server is encapsulated in the WebSocket protocol and is hidden from both the user and the application programmer, as a result of which the programmer implements his application in a created virtual environment similar to a single-user personal computer, without worrying or being puzzled by the problems of displaying information on client. These functions are performed by the proposed graphic object management system.

The proposed hybrid architecture is a system with the possibility of bidirectional communication (requests and responses in both directions), in which events from input devices are received by the browser, but with the ability to be translated and processed on the server; commands for drawing objects are executed on the client, which saves server resources. In this case, control of command delivery from the server is carried out by the network protocol; control from the application is not required.

The system contains user devices, a server, a network interface, includes user input devices, a Client, a local canvas (Canvas), as well as a server application layer and a GUI user interface located on the server, characterized by the ability of user input devices to broadcast data from input devices to the server application level, and the GUI user interface on the server with the ability to send a command to draw an object to the user’s local canvas (Canvas).

The user accesses through input devices and the Client sequentially through the network interface of the user and server to the server application layer, which, through the GUI user interface, sends a command to draw the object directly to the user's local canvas (Canvas). In this case, user input devices have the ability to access the server application level both directly and through the network interface, and the command to draw an object is sent both through the network interface and directly to the user’s local canvas (Canvas).

Just like in the RDP system version, we have advantages compared to WEB:

- bidirectional communication (requests and responses in both directions).

- events from input devices are accepted by the browser, but with the ability to be broadcast and processed on the server.

However, there are also significant differences:

- commands for drawing objects are executed on the client, which saves server resources.

- control of command delivery from the server is carried out by the network protocol; control from the application is not required.

The implementation of the proposed hybrid architecture is possible through the creation of a system containing an API program interface with the ability to manage developer applications and their interactions.

The system solves the following main tasks:

1. All applications are executed and interact on the server.

2. The single-threaded client displays output from parallel threads on the server (multi-threaded output).

3. Possibility of two-way data exchange between client and server.

4. Scalability of output data on the client.

5. Security of data from access from outside (from the client’s side).

The system consists of two parts:

1) Server part, with the ability to provide an API to third-party programs running on the server, as well as implement standard HTTPS and WebSocket Secure network protocols for connecting client browsers.

2) The client part, loaded by the web browser from the server part in the form of a standard HTML document containing client code written in JavaScript.

Advantages of using the proposed system:

1. We stop depending on the GUI implementation in browsers (cross-browser compatibility problems.)

2. The code becomes universal for any application, because it implements only graphic primitives (Canvas) and an exchange protocol with the server over WebSocket.

3. Synchronization of access to shared objects on the client is not needed, it occurs only on the server, which significantly increases the performance of applications (the time to request a lock to the server over the network and the server response is orders of magnitude longer than inside the server OS, and there is no problem of “hanging” locks in case of abnormal client disconnection).

4. Due to point 2, protection against unauthorized copying is increased not only of the application code, but also of application forms and components (forms, buttons, input fields are created only on the server, only a sequence of basic rendering functions is transferred to the client, from which no response data is required) .

5. We significantly increase network security due to the fact that we receive from the client only user input data (mouse movements, keyboard and touchpad presses, etc. input devices) - there is little data, so control is easier to implement compared to software interfaces where dozens of methods are used and properties for many objects.

6. Due to very fast synchronization, we are able to expand the functionality of web applications: create a full-fledged window manager with the ability to draw from N threads in N windows, and also redirect input from N users to one window, as in a regular OS.

7. You can transfer applications along with windows from user to user. For example, by opening the Notepad application on your desktop and writing text there, you can transfer it as an application to another user without saving the file or closing the application.

8. You can share one window for interactive or display-only collaboration with an unlimited number of users.

9. For each application there is no need to open a new page in the browser, but work as with a regular desktop.

10. You can implement a “stretched” desktop across several monitors, which do not have to be connected to one computer - synchronization and positioning will be provided by the server.

11. By obtaining functionality very close to terminal technologies (when a picture created on the server is copied), we at the same time relieve the server of drawing functions, because Canvas is brought to the client, which saves processor resources and memory allocated for virtual buffers. We also speed up the operation of applications - for example, an application, having called a client function to draw text, does not wait for execution to complete (control of command delivery from the server to the client occurs at the network level).

12. Our GUI is designed to be scalable, so the developer can add components specific to his application or offer sets of new visual components for sale to other developers if there are not enough built-in ones.

Advantages of the proposed system:

1. Uniformity in the display of information displayed on the screen.

2. User device resources are consumed to a minimum.

3. Applications run on the server side and interact with the user at the data input level.

4. Data security on the server (interception of client data on the server side is excluded).

5. Speed and ease of development of window procedures through the use of graphic primitives.

6. Full control over user processes and applications, as well as transferred client information on the server side.

7. The ability to create control and interaction between users, as well as monitoring user interaction from various structures (administrators, users, software).

8. The ability to implement DLP systems without the possibility of their detection or compromise by the user.

9. Significant increase in the productivity of custom application development due to two factors: lowering the barrier to entry for a developer; acceleration of development (item 5)

Technical task: to design a system to simplify the development of graphical interface applications for web browsers and expand their functionality, increase the security of data on the server, and reduce the consumption of user device resources.

The purpose of the invention is to create a system for managing developer applications and their interactions, providing a program interface (API) that solves the following main tasks:

- applications have the ability to run and interact on the server.

- on a single-threaded client, output from parallel threads on the server is displayed.

- possibility of two-way data exchange between client and server.

- scalability of output data on the client.

- data security from outside access (from the client).

The inventive system, including hardware devices (personal computers, input and output devices, server, computer network, etc.) contains two main parts:

the server part, which provides an API for third-party programs running on the server, and also implements standard HTTPS and WebSocket Secure network protocols for connecting browsers (clients);

the client part, downloaded by the web browser from the server part in the form of a standard HTML document containing client code written in JavaScript.

Thus, to solve this problem, a graphical object management system is proposed, containing a server part and a client part, while the server part is designed to provide an API to third-party programs running on the server, as well as implement standard HTTPS and WebSocket Secure network protocols for connecting browsers clients, and the client part is designed to be downloaded by a web browser from the server part in the form of a standard HTML document containing client code written in JavaScript. In this case, the system is designed to transmit data from the input devices of the client part and the Client sequentially through the network interface of the user and server to the server application level, from where, through the GUI user interface of the server part, the command to draw an object can be sent directly to the local Canvas canvas of the client part. In this case, user input devices have the ability to access the server application level both directly and through the network interface, and the command to draw an object from the GUI user interface of the server part is executable both through the network interface and directly to the local Canvas canvas of the client part.

The technical result is an increase in the productivity of interaction between the user and the server, an increase in the security of data on the server, and a decrease in the consumption of resources of the user device.

The technical result is achieved by the claimed graphical object management system, including control of elements of the graphical user interface GUI, containing server and client parts, characterized by the configuration of the server part with the ability to provide an API to third-party programs running on the server, with the ability to implement standard network protocols HTTPS and WebSocket Secure for connection client browsers; configuration of the client part containing local Canvas canvas, with the ability to be downloaded by a web browser from the server part in the form of a standard HTML document containing client code executed in JavaScript, containing a command to draw an object onto the local Canvas canvas of the client part, while control of the delivery of the drawing command from the server is carried out network protocol.

The graphical object management system is configured to transmit data from user input devices sequentially through the Client through the network interface of the user and server to the server application level, from where a command to draw an object can be implemented through the GUI user interface of the server part to the local Canvas canvas of the client part.

In this case, the client part is designed to transmit data from input devices directly to the server application level. The client part is also designed to transmit data from input devices to the server application level via a network interface.

The graphical object management system is designed in such a way that a command from the server to draw an object can be implemented through the network interface, in addition, a command from the server to draw an object can be implemented directly on the local Canvas canvas of the client part.

The essence of the proposed technical solution is illustrated by the images in Fig. 1-4.

Fig. 1. Architecture (level interaction system) of a local single-user application - a personal computing device.

Fig. 2. Architecture (user-server interaction system) WEB

Fig. 3. Architecture (system of interaction between levels) of the user and server.

Fig. 4. A system for managing graphic objects using the example of interaction between a user and a server using a hybrid architecture.

Implementation example

The graphics subsystems of all popular Operating Systems (OC) can be divided into two logical levels:

1. Graphical User Interface (GUI):

Includes interactive elements: window manager, buttons, input fields, drop-down lists and others that allow the user to interact using input devices (keyboard, mouse, etc.) with the program (application, because the program uses OS functions rather than implementing these elements itself)

2. Graphic Output Device:

Consists of a basic object for outputting raster graphics to the monitor. It is a two-dimensional array of pixels (usually called Canvas) and basic functions for generating raster images: contours and filling the contour with color, straight lines, points, Bezier curves, text output (character contours in modern fonts are described by Bezier curves), and also copying sections of images from other canvases.

To solve the problem of the most effective management of graphic objects and application development, it is proposed to transform the system for providing and exchanging information at the application (upper) level of the OSI model, transmitted through any computer network (LAN, Internet).

The proposed solution is to partially transfer the functions of the graphics system to the server side (specifically, GUI/UI). We will use the Canvas object for this, as well as to capture events from input devices.

To solve the one-way direction of request initiation, we will use the new WebSocket transport protocol. (Both objects are described in the HTML5 standard, supported by all modern browsers).

All data exchange between the Client and the Server is encapsulated in the WebSocket protocol and is hidden from both the user and the application programmer, as a result of which the programmer implements his application in a created virtual environment similar to a single-user personal computer, without worrying or being puzzled by the problems of displaying information on the Client . These functions are performed by the proposed control system.

The proposed hybrid architecture (Fig. 4) is a system with bidirectional communication capabilities (requests and responses in both directions). Events from input devices are received by the browser, but with the ability to be broadcast and processed on the server. Object rendering commands are executed on the client, which saves server resources. Control of command delivery from the server is carried out by the network protocol; control from the application is not required.

The system contains (Fig. 4) user devices, a server, a network interface, includes user input devices, a Client, a local Canvas canvas, as well as a server application layer and a GUI user interface located on the server, characterized by the ability of user input devices to broadcast data from input devices to the server application level, and the GUI user interface on the server with the ability to send a command to draw an object to the user’s local Canvas canvas.

The user accesses through input devices and the Client through the network interface of the user and server sequentially to the server application layer, which, through the GUI user interface, sends a command to draw the object directly to the user's local Canvas. In this case, user input devices have the ability to access the server application level both directly and through the network interface, and the command to draw an object is sent both through the network interface and directly from the GUI user interface of the server part to the local Canvas user canvas of the client part.

Thus, the advantages compared to WEB are realized:

- Bidirectional communication (requests and responses in both directions).

- Events from input devices are received by the browser, but with the ability to be broadcast and processed on the server.

Significant differences:

- Object drawing commands are executed on the client. which saves server resources.

- Control of command delivery from the server is carried out by the network protocol; control from the application is not required.

The implementation of this hybrid architecture is possible through the creation of a system containing a program interface (API) with the ability to manage developer applications and their interactions.

The system solves the main tasks:

- All applications are executed and interact on the server.

- On a single-threaded client, output from parallel threads on the server is displayed (multi-threaded output).

- Possibility of two-way data exchange between client and server.

- Scalability of output data on the client.

- Data security from access from outside (from the client side).

As a result, the system consists of two main parts:

server part, with the ability to provide an API to third-party programs running on the server, as well as implement standard HTTPS and WebSocket Secure network protocols for connecting browsers (clients).

the client part, loaded by the web browser from the server part in the form of a standard HTML document containing client code written in JavaScript.

What do we get from using the proposed system:

1. We stop depending on the GUI implementation in browsers (cross-browser compatibility problems.)

2. The code becomes universal for any application, because it implements only graphic primitives (Canvas) and an exchange protocol with the server over WebSocket.

3. Synchronization of access to shared objects on the client is not needed, it occurs only on the server, which significantly increases the performance of applications (the time to request a lock to the server over the network and the server response is orders of magnitude longer than inside the server OS, and there is no problem of “hanging” locks in case of abnormal client disconnection).

4. Due to point 2, protection against unauthorized copying is increased not only of the application code, but also of application forms and components (forms, buttons, input fields are created only on the server, only a sequence of basic rendering functions is transferred to the client, from which no response data is required) .

5. We significantly increase network security due to the fact that we receive from the client only user input data (mouse movements, keyboard and touchpad presses, etc. input devices) - there is little data, so control is easier to implement compared to software interfaces where dozens of methods are used and properties for many objects.

6. Due to very fast synchronization, we are able to expand the functionality of web applications: create a full-fledged window manager with the ability to draw from N threads in N windows, and also redirect input from N users to one window, as in a regular OS.

7. You can transfer applications along with windows from user to user. For example, by opening the Notepad application on your desktop and writing text there, you can transfer it as an application to another user without saving the file or closing the application.

8. You can share one window for interactive or display-only collaboration with an unlimited number of users.

9. For each application there is no need to open a new page in the browser, but work as with a regular desktop.

10. You can implement a “stretched” desktop across several monitors, which do not have to be connected to one computer - synchronization and positioning will be provided by the server.

11. By obtaining functionality very close to terminal technologies (when a picture created on the server is copied), we at the same time relieve the server of drawing functions, because Canvas is brought to the client, which saves processor resources and memory allocated for virtual buffers. We also speed up the operation of applications - for example, an application, having called a client function to draw text, does not wait for execution to complete (control of command delivery from the server to the client occurs at the network level).

12. Our GUI is designed to be scalable, so the developer can add components specific to his application or offer sets of new visual components for sale to other developers if there are not enough built-in ones.

Advantages of the proposed system:

1. Uniformity in the display of information displayed on the screen.

2. User device resources are consumed to a minimum.

3. Applications run on the server side and interact with the user at the data input level.

4. Data security on the server (interception of client data on the server side is excluded).

5. Speed and ease of development of window procedures through the use of graphic primitives.

6. Full control over user processes and applications, as well as transferred client information on the server side.

7. The ability to create control and interaction between users, as well as monitoring user interaction from various structures (administrators, users, software).

8. The ability to implement DLP systems without the possibility of their detection or compromise by the user.

9. Significant increase in the productivity of custom application development due to two factors: lowering the barrier to entry for a developer; acceleration of development (clause 5)

The graphical object management system contains a server part and a client part. The server part is designed to provide an API to third-party programs running on the server, as well as implement standard HTTPS and WebSocket Secure network protocols for connecting browsers (clients).

The client part is loaded by the web browser from the server part in the form of a standard HTML document containing client code written in JavaScript.

In this case, the user accesses through input devices and an RDP client through the network interface of the user and server sequentially to the server application level, which, through the user interface, sends a command to draw the object immediately to the user’s local canvas. In this case, user input devices have the ability to access the server application level both directly and through the network interface, and the command to draw an object is sent both through the network interface and directly to the user’s local canvas.

The proposed technical solution consists in partially moving the functions of the graphical system to the server side (specifically, GUI/UI). For this we will use the Canvas object, as well as to capture events from input devices.

To solve the one-way direction of request initiation, we will use the new WebSocket transport protocol. Both objects are described in the HTML5 standard and are supported by all modern browsers.

Claims (6)

1. A graphical object management system, including management of elements of the graphical user interface GUI, containing server and client parts, characterized by the configuration of the server part with the ability to provide an API to third-party programs running on the server, with the ability to implement standard network protocols HTTPS and WebSocket Secure for connecting client browsers ; configuration of the client part containing the local Canvas canvas, with the ability to be downloaded by a web browser from the server part in the form of a standard HTML document containing client code executed in JavaScript, containing a command for drawing an object to the local Canvas canvas of the client part, while controlling the delivery of the command for rendering from the server is carried out using a network protocol. 2. The graphical object management system according to claim 1, characterized in that it is designed to transmit data from user input devices sequentially through the Client through the network interface of the user and server to the server application level, from where a command can be implemented through the GUI user interface of the server part drawing an object to the local Canvas canvas of the client part. 3. The graphical object management system according to claim 1, characterized in that the client part is designed to transmit data from input devices directly to the server application level. 4. The graphical object management system according to claim 1, characterized in that the client part is configured to transmit data from input devices to the server application level via a network interface. 5. The graphical object management system according to claim 1, characterized in that a command from the server to draw an object can be implemented via a network interface. 6. The graphical object management system according to claim 1, characterized in that the command from the server to draw an object can be implemented directly on the local Canvas canvas of the client part.