CN107872492B - Method and device for supporting multi-user editing of data object at server - Google Patents
Method and device for supporting multi-user editing of data object at server Download PDFInfo
- Publication number
- CN107872492B CN107872492B CN201610859683.5A CN201610859683A CN107872492B CN 107872492 B CN107872492 B CN 107872492B CN 201610859683 A CN201610859683 A CN 201610859683A CN 107872492 B CN107872492 B CN 107872492B
- Authority
- CN
- China
- Prior art keywords
- client
- data
- editing
- push
- data object
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
Abstract
The invention provides a method and a device for supporting multi-user editing of data objects at a server side, which can reduce the bandwidth and network resource consumption of a server, improve the load capacity of the server, ensure the normal real-time synchronization of multi-user editing data under a distributed cluster deployment environment, enable users to see the editing actions of other users in real time, realize multi-user cooperative office and accurate data push, and improve the working efficiency. The invention discloses a method for supporting multi-user editing of data objects at a server, which comprises the following steps: receiving an editing request of a client to a data object; verifying the authority of the client, and refusing the editing request when the client does not belong to the user group, and ending the method; establishing an editing connection with the client and monitoring the modification of the data object by the client; when the modification meets the conditions in the data modification pushing condition set, pushing the modified data object to all other users except the client in the user group; and when the client quits the editing, closing the editing connection with the client.
Description
Technical Field
The present invention relates to the field of computer and software technologies thereof, and in particular, to a method and an apparatus for supporting multi-user editing of data objects at a server.
Background
With the development of internet technology, data edited on one client can be synchronized to other clients of the system through a server. According to the currently commonly used scheme, the client updates the data of the server mainly by means of polling and Comet (a server push technology). The polling mode is mainly to set a specific time interval, the browser sends an interface calling request to the server at each time interval point, and then the server returns the latest data to the browser of the client, so as to achieve the effect that the page can reflect the data change of the server in time. The Comet method mainly utilizes a technology (adopting Comet technology based on ajax long polling) for simulating two-way communication between a client and a server.
Specifically, the process of the client updating data from the server by polling and Comet technology is described in detail below in conjunction with fig. 1 and 2, respectively.
As shown in fig. 1, the updating of data from the server by the client through the polling technique mainly includes the following processes:
a timer (such as 2 seconds) is set in the front-end page JS, and a data request is initiated to the server end in a timing cycle;
the server side returns the page to display the required data according to the service after receiving the request;
if the server does not return data, the client (browser) continues to initiate data requests to the server when the timing time is reached.
As shown in fig. 2, the client updating data from the server through Comet technology mainly includes the following processes:
after the front-end page is loaded, establishing a long HTTP connection (such as connection 1, connection 2 and the like) between the ajax (asynchronous JavaScript and XML) and the server;
if the server side has no data updating, no data is returned, and the current request enters a dormant state;
if the sleep time exceeds the set timeout time, the server will return a blocking request (send a timeout prompt) and close the current connection, and the front-end page will initiate a new request to the server after processing the request and re-establish a new long connection;
if the service end has a service data change event trigger (namely, data update), the service end immediately returns the requested data, then closes the current connection, and after the client finishes processing the returned data, the client re-initiates the request to the service end again and re-establishes a new long connection.
FIG. 3 is a schematic diagram illustrating an implementation process of updating data from a server by a client through Comet technology. As shown in fig. 3, after the connection between the client and the server is established, the server checks whether the service data has changed, if yes, returns data to the client and closes the current connection, and the process is ended, otherwise, the current request enters a sleep state to wait for a data change notification; after the current request enters a sleep state, whether the sleep time of the current request is overtime is checked, if yes, an overtime prompt is returned to the client side and the current connection is closed, and if not, a data change notification is waited until the service data of the server side is changed, data is returned to the client side and the current connection is closed.
The above solutions for updating data from the server by polling and Comet technologies at the client have many disadvantages: first, the polling method is used, so that the transmitted request cannot return changed data every time, which wastes server bandwidth, and continuously requests server resources, thereby increasing server pressure. Secondly, in the scene of editing the table online by multiple people simultaneously in a Comet mode, because the frequency of data synchronization is very high, a connection is newly established when the Comet finishes data response every time, and thus, the Comet mechanism can cause the waste of bandwidth and the increase of server pressure.
Disclosure of Invention
In view of the above, the present invention provides a method and an apparatus for supporting multiple users to edit a data object at a server, which can reduce bandwidth and network resource consumption of a server, improve load capacity of the server, facilitate later maintenance and expansion, reduce maintenance cost of software, ensure normal real-time synchronization of multiple users editing data in a distributed cluster deployment environment, support real-time online of multiple users, enable users to synchronously see editing actions of other users in real time, achieve the purpose of multi-user cooperative office, improve work efficiency, and implement accurate pushing of data.
To achieve the above object, according to one aspect of the present invention, a method for supporting multi-user editing of data objects at a server is provided.
A method of supporting multi-user editing of data objects at a server, each data object having an associated set of user groups and data modification push conditions, the method comprising: receiving an editing request of a client to the data object; verifying the authority of the client, and refusing the editing request when the client does not belong to the user group, and ending the method; establishing an editing connection with the client and monitoring the client for modifications to the data object; when the modification meets the conditions in the data modification pushing condition set, pushing the modified data object to all other users except the client in the user group; and when the client quits the editing, closing the editing connection with the client.
Optionally, the server includes a data pushing manager, and establishes an editing connection with the client using the data pushing manager, monitors modification of the data object by the client, and pushes the modified data object to all other users in the user group except the client.
Optionally, the establishing of the edit connection with the client includes storing a corresponding connection ID, user information of the client, and edit connection information of other users in the user group.
Optionally, the data modification push condition set includes the following conditions: the modification data exceeds 3 characters, and the modification time exceeds 3 seconds.
Optionally, wherein the user group of the data object is defined when the data object is created.
Optionally, when a failure occurs when pushing the modified data object to all other users except the client in the user group, a retry mechanism is entered, and if the failure still occurs after the retry, a failure prompt is sent to the client.
Optionally, wherein the data object is a data table.
According to another aspect of the present invention, an apparatus for supporting multi-user editing of data objects at a server is provided.
An apparatus for supporting multi-user editing of data objects at a server, each data object having an associated set of user groups and data modification push conditions, the apparatus comprising: the receiving module is used for receiving an editing request of a client to the data object; the verification module is used for verifying the authority of the client, and refusing the editing request when the client does not belong to the user group, and the method is ended; the pushing module is used for establishing an editing connection with the client and monitoring the modification of the data object by the client; when the modification meets the conditions in the data modification pushing condition set, pushing the modified data object to all other users except the client in the user group; and when the client quits the editing, closing the editing connection with the client.
Optionally, the server includes a data push manager, and the push module is further configured to: and establishing an editing connection with the client by using the data pushing manager, monitoring the modification of the client to the data object, and pushing the modified data object to all other users except the client in the user group.
Optionally, the pushing module is further configured to: and storing the corresponding connection ID, the user information of the client and the editing connection information of other users in the user group.
Optionally, the data modification push condition set includes the following conditions: the modification data exceeds 3 characters, and the modification time exceeds 3 seconds.
Optionally, wherein the user group of the data object is defined when the data object is created.
Optionally, the pushing module is further configured to: and when the modified data object is pushed to all other users except the client in the user group, failure occurs, a retry mechanism is entered, and if the failure still occurs after retry, a failure prompt is sent to the client.
Optionally, wherein the data object is a data table.
According to the technical scheme of the invention, an editing request of a client to a data object is received, the authority of the client is verified, when the client does not belong to a user group, the editing request is rejected, the method is ended, if the client belongs to the user group, an editing connection with the client is established, the modification of the client to the data object is monitored, when the modification meets the condition of data modification pushing condition concentration, the modified data object is pushed to all other users except the client in the user group, and when the client quits editing, the editing connection with the client is closed. By using the technical scheme of the invention, only one websocket connection is maintained between one client and the server, the bandwidth and network resource consumption of the server are reduced, the load capacity of the server is improved, the later maintenance and expansion are facilitated, the maintenance cost of software is reduced, the normal real-time synchronization of multi-user editing data in a distributed cluster deployment environment is ensured, the real-time online of multiple users is supported, the users can synchronously see the editing actions of other users in real time, the purpose of multi-user cooperative office work is achieved, the working efficiency is improved, and in addition, the data is accurately pushed to users with authority.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a diagram illustrating a process of a client updating data from a server through a polling technique according to the prior art;
FIG. 2 is a diagram illustrating a process of a client updating data from a server through Comet technology in the prior art;
FIG. 3 is a schematic diagram of a prior art implementation process of updating data from a server by a client through Comet technology;
FIG. 4 is a diagram illustrating the main steps of a method for supporting multi-user editing of data objects at a server according to an embodiment of the present invention;
FIG. 5 is a block diagram of an overall framework supporting multi-user editing of data objects at a server in accordance with an embodiment of the invention;
FIG. 6 is a flowchart illustrating an implementation of supporting multi-user editing of data objects at a server according to an embodiment of the present invention;
fig. 7 is a schematic diagram of main modules of an apparatus for supporting multi-user editing of a data object at a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 4 is a schematic diagram of the main steps of a method for supporting multi-user editing of data objects at a server according to an embodiment of the present invention.
As shown in fig. 4, the method for supporting multi-user editing of data objects at a server according to an embodiment of the present invention mainly includes the following steps S401 to S403. Each data object has an associated user group and a data modification push condition set, and the data object may be a data table, or may be a data object in other forms pushed to a web page side or a mobile phone side.
Step S401: and receiving an editing request of a client to the data object.
Step S402: and verifying the authority of the client, and refusing the editing request when the client does not belong to the user group.
The authority of the client is mainly used for verifying whether the client has the authority for editing the data object, a user group can be defined when the data object is created, and all users in the user group are specified to have the authority for editing the data object.
If the client does not belong to the user group, the editing request of the client is rejected, and if the client belongs to the user group, the editing request of the client is passed, and step S403 is performed.
Step S403: and establishing an editing connection with the client, monitoring the modification of the client to the data object, pushing the modified data object to all other users except the client in the user group when the modification meets the condition of the data modification pushing condition set, and closing the editing connection with the client when the client quits the editing.
The server side mainly establishes an editing connection with the client side through the data pushing manager, monitors modification of the client side on the data object and pushes the modified data object to all other users except the client side in the user group.
Specifically, establishing an editing connection with a client mainly includes: and storing the corresponding connection ID, the user information of the client and the editing connection information of other users in the user group.
The data modification push condition set may specifically include the following conditions: the modification data exceeds 3 characters, and the modification time exceeds 3 seconds.
And when failure occurs when the modified data object is pushed to all other users except the client in the user group, entering a retry mechanism, and if failure still occurs after retry, sending a failure prompt to the client.
FIG. 5 is a block diagram illustrating an overall framework for supporting multi-user editing of data objects at a server according to an embodiment of the present invention.
The server establishes an editing connection with the client through the data pushing manager, monitors the modification of the client to the data object and pushes the modified data object to all other users except the client in the user group. As shown in fig. 5, the data Push Manager can be implemented by a Push Manager of the Server, where the Push Manager is a distributed cluster service for managing websocket connections developed based on a Netty framework (a programming framework for rapidly developing network clients/servers), and includes two services, namely, a Push Server (Push Server) and a Push Client (Push Client). The Push Server is used for allocating connection between the Client and the Push Client, and in order to balance load, the Push Server generally allocates the Push Client with the least number of Client connections, and the Push Client is responsible for establishing editing connection with the Client. The Push Client is used for establishing connection between the clients and pushing the data object to the clients. The data objects in fig. 5 are exemplified by data tables, and the data push manager saves the connection ID of the client, the user information of the client, and the edit connection information of other users in the user group to a storage system, such as a Redis storage system, through a corresponding table service.
According to the general framework shown in fig. 5 for supporting multi-user editing of a data object at a server, a specific implementation flow of supporting multi-user editing of a data object at a server according to an embodiment of the present invention is shown in fig. 6, and specifically includes the following steps S601 to S615.
Step S601: the server receives a request for editing the data table from the client.
Wherein the form can be created by the client or other clients, and the creator of the form adds all client users who can use the form to a user group when creating the form, and only the users in the user group have the right to edit the form.
Step S602: the server side verifies whether the client side has the authority of editing the table, if so, the step S603 is executed, otherwise, the step S604 is executed.
The authority of the client is verified mainly to ensure data security and prevent illegal users who are not in a user group from editing and modifying data in the form.
Step S603: and the client requests to establish an editing connection to a data push manager of the server.
After the step S603 is executed, a step S605 is executed.
Step S604: the client is denied an edit request to the data form.
Step S605: and judging whether the connection is successfully established, if not, executing the step S606, and if so, executing the step S609.
Step S606: the establishment of the edit connection is retried and the next step S607 is executed.
Step S607: and judging whether the retry operation is successful, if so, executing step 609, otherwise, executing step 608.
Step S608: and the server side returns a prompt message of connection failure to the client side.
Step S609: the data push manager processes the connection request of the client and stores the connection ID and the user information of the client in the storage system.
Specifically, after receiving a connection request of a Client, the data Push manager is processed by a Push Server (Push Server), the Push Server obtains the sum of the Client connection number of each Push Client (Push Client), and finds out the Push Client with the least Client connection number through comparison, so that the Push Client is responsible for establishing an editing connection with the Client, and thus, the load balance of the clients connected to the Push clients can be ensured. Then, the pushServer sends the connection ID, the user information and the like of the Push Client and the Client to the corresponding table service, the table service adds the connection ID and the user information to the user group and stores the user group in a storage system (such as Redis), and finally the connection information such as the connection ID, the user information and the like is returned to the Client so that the Client can establish connection with the Push Client according to the connection information.
The user group also includes the edit connection information (including connection ID and user information) of other users in the group, and when these users establish edit connection with the server, the table service will store these information in the storage system, when some user exits the table edit function, the corresponding edit connection of this user will be closed, and the edit connection information of this user will be moved out of this user group at the same time.
Step S610: and the client side edits the data form and submits the edited data to the corresponding form service of the server side when the condition of the data modification pushing condition set is reached.
The conditions in the data modification and pushing condition set are preset by a client user according to requirements, and specifically include the following conditions: the modification data exceeds 3 characters, and the modification time exceeds 3 seconds.
Step S611: the form service of the server notifies the data push manager to perform data push.
Step S612: the data push manager pushes data to all other users in the user group except the client.
Step S613: the server determines whether the data pushing is successful, if so, executes step S614, otherwise, executes step S615.
Step S614: and other users receiving the data update the data according to the pushed data.
Step S615: and the data pushing manager retries the data pushing, and if the data pushing fails to retry, returns a prompt message of the pushing failure to the client.
If the retry fails, the client can notify other users to update the data in the table through offline after receiving the prompt message of push failure returned by the server.
When the Client exits the form editing function, the data Push manager closes the Push Client's editing connection with the Client, and the form service removes the Client's connection ID and user information from the user group.
The technical scheme of the embodiment of the invention is based on the characteristics of high performance and high reliability of Netty, and the data Push Manager (Push Manager) for managing the websocket connection is developed, so that the client and the server can constantly keep a data communication pipeline, and when the server has the change of service data (such as table data), the server can actively, timely and reliably send the latest data to the client.
Fig. 7 is a schematic diagram of main modules of an apparatus for supporting multi-user editing of a data object at a server according to an embodiment of the present invention. The data objects may be data tables, each data object having an associated set of users and a set of data modification push conditions.
Fig. 7 shows an apparatus 700 for supporting multi-user editing of a data object at a server according to an embodiment of the present invention, which mainly includes a receiving module 701, a verifying module 702, and a pushing module 703. The receiving module 701 is configured to receive an editing request of a client for a data object; the verification module 702 is configured to verify the authority of the client, and when the client does not belong to the user group, reject the editing request, and the method ends; the push module 703 is used to establish an edit connection with the client and monitor the client for modifications to the data object; when the modification meets the conditions in the data modification pushing condition set, pushing the modified data object to all other users except the client in the user group; and when the client quits the editing, closing the editing connection with the client.
The server may include a data pushing manager, and the pushing module 703 may be configured to establish an editing connection with the client using the data pushing manager, monitor the modification of the data object by the client, and push the modified data object to all other users in the user group except the client.
The push module 703 may also be configured to store the corresponding connection ID, the user information of the client, and the connection editing information of other users in the user group.
The set of data modification push conditions may include the following conditions: the modification data exceeds 3 characters and the modification time exceeds 3 seconds.
The user group of the data object is defined when the data object is created.
The push module 703 may also be used to: and when the modified data object is pushed to all other users except the client in the user group, failure occurs, a retry mechanism is entered, and if failure still occurs after retry, a failure prompt is sent to the client.
According to the technical scheme of the embodiment of the invention, an editing request of a client to a data object is received, the authority of the client is verified, when the client does not belong to a user group, the editing request is rejected, the method is ended, if the client belongs to the user group, an editing connection with the client is established, the modification of the client to the data object is monitored, when the modification meets the condition of data modification pushing condition concentration, the modified data object is pushed to all other users except the client in the user group, and when the client quits editing, the editing connection with the client is closed. By using the technical scheme of the embodiment of the invention, only one websocket connection is maintained between one client and the server, the bandwidth and network resource consumption of the server are reduced, the load capacity of the server is improved, the later maintenance and expansion are facilitated, the maintenance cost of software is reduced, the normal real-time synchronization of multi-user editing data in a distributed cluster deployment environment is ensured, the real-time online of multiple users is supported, the users can synchronously see the editing actions of other users in real time, the purpose of multi-user cooperative office work is achieved, the working efficiency is improved, and in addition, the data is accurately pushed to users with authority.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (12)
1. A method of supporting multi-user editing of data objects at a server, each data object having an associated set of user groups and data modification push conditions, the method comprising:
receiving an editing request of a client to the data object;
verifying the authority of the client, and refusing the editing request when the client does not belong to the user group, and ending the method;
establishing an edit connection with the client using a data push manager and monitoring modifications to the data object by the client; the data push manager comprises a push server service and a push client service, one push client service with the least number of client connections is obtained through the push server service, and the push client service establishes an editing connection with the client;
when the modification meets the conditions in the data modification pushing condition set, pushing the modified data object to all other users except the client in the user group;
and when the client quits the editing, closing the editing connection with the client.
2. The method of claim 1, wherein establishing an edit connection with the client comprises saving a corresponding connection ID, user information for the client, and edit connection information for other users in the user group.
3. The method of claim 1, wherein the set of data modification push conditions includes conditions for:
modifying the data over 3 characters, an
The modification time exceeds 3 seconds.
4. The method of claim 1, wherein the group of users of the data object is defined when the data object is created.
5. The method of claim 1, wherein a failure occurs when pushing the modified data object to all other users in the group of users except the client, entering a retry mechanism, and if the failure remains after the retry, sending a failure prompt to the client.
6. The method of claim 1, wherein the data object is a data table.
7. An apparatus for supporting multi-user editing of data objects at a server, each data object having an associated set of user groups and data modification push conditions, the apparatus comprising:
the receiving module is used for receiving an editing request of a client to the data object;
the verification module is used for verifying the authority of the client, and refusing the editing request when the client does not belong to the user group, and the method is ended;
the pushing module is used for establishing an editing connection with the client by using a data pushing manager and monitoring the modification of the data object by the client; the data push manager comprises a push server service and a push client service, one push client service with the least number of client connections is obtained through the push server service, and the push client service establishes an editing connection with the client; when the modification meets the conditions in the data modification pushing condition set, pushing the modified data object to all other users except the client in the user group; and when the client quits the editing, closing the editing connection with the client.
8. The apparatus of claim 7, wherein the pushing module is further to: and storing the corresponding connection ID, the user information of the client and the editing connection information of other users in the user group.
9. The apparatus of claim 7, wherein the set of data modification push conditions includes conditions to:
modifying the data over 3 characters, an
The modification time exceeds 3 seconds.
10. The apparatus of claim 7, wherein the group of users of the data object is defined when the data object is created.
11. The apparatus of claim 7, wherein the pushing module is further to: and when the modified data object is pushed to all other users except the client in the user group, failure occurs, a retry mechanism is entered, and if the failure still occurs after retry, a failure prompt is sent to the client.
12. The apparatus of claim 7, wherein the data object is a data table.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610859683.5A CN107872492B (en) | 2016-09-28 | 2016-09-28 | Method and device for supporting multi-user editing of data object at server |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610859683.5A CN107872492B (en) | 2016-09-28 | 2016-09-28 | Method and device for supporting multi-user editing of data object at server |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107872492A CN107872492A (en) | 2018-04-03 |
| CN107872492B true CN107872492B (en) | 2021-05-25 |
Family
ID=61761036
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610859683.5A Active CN107872492B (en) | 2016-09-28 | 2016-09-28 | Method and device for supporting multi-user editing of data object at server |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107872492B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109299046B (en) * | 2018-08-30 | 2023-08-15 | 湖北工业大学 | Collaborative editing method based on TCP WebSocket protocol |
| CN109522533A (en) * | 2018-10-12 | 2019-03-26 | 平安科技（深圳）有限公司 | Table edit method, apparatus, equipment and medium based on web data |
| CN111865687B (en) * | 2020-07-20 | 2023-05-30 | 上海万物新生环保科技集团有限公司 | Service data updating method and device |
| CN112800742B (en) * | 2021-04-14 | 2022-04-01 | 北京智慧易科技有限公司 | Method, system and equipment for compiling standard file |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102521407A (en) * | 2011-12-28 | 2012-06-27 | 谢勇 | Method for document collaboration among users |
| CN103347091A (en) * | 2013-07-19 | 2013-10-09 | 百度在线网络技术（北京）有限公司 | Method for sharing document annotations and cloud server |
| CN104572600A (en) * | 2013-10-29 | 2015-04-29 | 镇江睿泰信息科技有限公司 | Multi-person collaborative document editing operation method |
| CN105743973A (en) * | 2016-01-22 | 2016-07-06 | 上海科牛信息科技有限公司 | Multi-user multi-device real-time synchronous cloud cooperation method and system |
-
2016
- 2016-09-28 CN CN201610859683.5A patent/CN107872492B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102521407A (en) * | 2011-12-28 | 2012-06-27 | 谢勇 | Method for document collaboration among users |
| CN103347091A (en) * | 2013-07-19 | 2013-10-09 | 百度在线网络技术（北京）有限公司 | Method for sharing document annotations and cloud server |
| CN104572600A (en) * | 2013-10-29 | 2015-04-29 | 镇江睿泰信息科技有限公司 | Multi-person collaborative document editing operation method |
| CN105743973A (en) * | 2016-01-22 | 2016-07-06 | 上海科牛信息科技有限公司 | Multi-user multi-device real-time synchronous cloud cooperation method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107872492A (en) | 2018-04-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107872492B (en) | Method and device for supporting multi-user editing of data object at server | |
| CN107528891B (en) | Websocket-based automatic clustering method and system | |
| KR102208935B1 (en) | Messaging api over http protocol to establish context for data exchange | |
| US11741075B2 (en) | Methods and system of tracking transactions for distributed ledger | |
| CN101605108A (en) | A kind of method, system and device of instant messaging | |
| WO2016120730A1 (en) | Highly scalable, fault tolerant remote access architecture and method of connecting thereto | |
| CN108390950A (en) | A kind of information push method, device and equipment | |
| CN105187372A (en) | Method for data processing based on mobile application entrance, device and system | |
| CN105681454A (en) | Method and system for self-adaptively connecting cloud desktop | |
| CN105592035A (en) | Single sign on method used for multiple application systems | |
| US9152441B2 (en) | Systems and methods involving virtual machine host isolation over a network via a federated downstream cluster | |
| US20220116400A1 (en) | Authorization in communication networks | |
| EP2605460A1 (en) | Method, apparatus, and system for transferring file to user of instant message system | |
| WO2014152076A1 (en) | Retry and snapshot enabled cross-platform synchronized communication queue | |
| CN102215266A (en) | Implementation method of persistency services and persistency service system | |
| CN111953784B (en) | Asynchronous communication framework-based file transmission method, device and system | |
| WO2017215408A1 (en) | Session switching control method and apparatus and access point device | |
| CN107517227A (en) | Session implementation method and device for distributed consensus system | |
| WO2017097181A1 (en) | Data pushing method and apparatus | |
| CN105490861A (en) | System and method of management of network management device | |
| US9270528B2 (en) | Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices | |
| CN108040072A (en) | The system and method for mobile Internet APP single-sign-ons under distributed network | |
| CN106657360A (en) | Synchronization method and system for NIS servers under Linux system | |
| CN109040331B (en) | Electronic business card processing method and device, computing equipment and storage medium | |
| WO2013189421A2 (en) | Distributed call ticket statistical method, device and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |