CN116248502A - Method, device and system for updating user-related data local to browser - Google Patents

Method, device and system for updating user-related data local to browser Download PDF

Info

Publication number
CN116248502A
CN116248502A CN202310210447.0A CN202310210447A CN116248502A CN 116248502 A CN116248502 A CN 116248502A CN 202310210447 A CN202310210447 A CN 202310210447A CN 116248502 A CN116248502 A CN 116248502A
Authority
CN
China
Prior art keywords
identification information
browser
local
update identification
updating
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.)
Pending
Application number
CN202310210447.0A
Other languages
Chinese (zh)
Inventor
谢星
黄浩
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shanghai Yunzhou Information Technology Co ltd
Original Assignee
Shanghai Yunzhou Information Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Shanghai Yunzhou Information Technology Co ltd filed Critical Shanghai Yunzhou Information Technology Co ltd
Priority to CN202310210447.0A priority Critical patent/CN116248502A/en
Publication of CN116248502A publication Critical patent/CN116248502A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/0816—Configuration setting characterised by the conditions triggering a change of settings the condition being an adaptation, e.g. in response to network events
    • 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]
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The application aims to provide a method, equipment and a system for updating user-related data local to a browser. Specifically, the server returns an HTTP response message to the browser based on an HTTP request message sent by the browser, wherein a response header of the HTTP response message contains update identification information; the browser judges whether the local update identification information is consistent with the update identification information in the response head; if the update identification information of the local browser is inconsistent with the update identification information in the response header, updating the user related data of the local browser, and updating the update identification information of the local browser into the update identification information in the response header. According to the browser-side JS file updating method and device based on the B/S architecture, after the JS file at the browser side is updated, the local user-related data of the browser is automatically updated, the operation reliability is high, the efficiency is high, manual operation by a user is not needed, and therefore user experience is optimized.

Description

Method, device and system for updating user-related data local to browser
Technical Field
The present application relates to the field of information technology, and in particular, to a technology for updating user related data local to a browser.
Background
When a server based on a B/S architecture (Browser and server architecture, browser/Server Architecture) is updated, user related data (such as user identity, license, etc.) originally stored in the Browser may need to be updated accordingly, but the server software is not updated in general. At this time, a problem arises if a new version of JS (JavaScript) program is run on the browser side to parse the old version of user-related data. There are two main solutions currently in common use: (1) After the software is upgraded, the user manually cleans the local data of the browser; (2) not modifying the old version of the data structure. However, if the user manually cleans the local data of the browser, the manual operation is complicated, and the user experience is poor; if the old version of the data structure is not modified, then there are defects in the software design.
Disclosure of Invention
An object of the present application is to provide a method, apparatus and system for updating user-related data local to a browser.
According to one aspect of the present application, there is provided a method for updating user-related data local to a browser, wherein the method comprises:
based on an HTTP request message sent by a browser, a server returns an HTTP response message to the browser, wherein a response header of the HTTP response message contains update identification information;
the browser judges whether the local update identification information is consistent with the update identification information in the response head;
if the update identification information of the local browser is inconsistent with the update identification information in the response header, updating the user related data of the local browser, and updating the update identification information of the local browser into the update identification information in the response header.
Further, if the corresponding update identification information does not exist in the local browser, that is, the update identification information in the local browser is inconsistent with the update identification information in the response header, updating the user related data in the local browser, and writing the update identification information in the response header into the local browser.
Further, if the corresponding update identification information exists locally in the browser, but the update identification information in the local browser is inconsistent with the update identification information in the response header, updating the user related data in the local browser, and updating the update identification information in the local browser to the update identification information in the response header.
Further, if the corresponding update identification information exists locally in the browser, and the update identification information locally in the browser is consistent with the update identification information in the response header, the operation of updating the user related data locally in the browser is not performed.
Further, the update identification information includes version number information.
According to another aspect of the present application, there is also provided a method for updating local user-related data applied to a browser, where the method includes:
an HTTP request message is sent to a server, and an HTTP response message returned by the server is received, wherein a response header of the HTTP response message contains update identification information;
judging whether the local update identification information is consistent with the update identification information in the response head;
if the local updating identification information is inconsistent with the updating identification information in the response head, updating the local user related data, and updating the local updating identification information into the updating identification information in the response head.
According to yet another aspect of the present application, there is also provided a system for updating user-related data local to a browser, wherein the system comprises a browser and a server;
the server returns an HTTP response message to the browser based on the HTTP request message sent by the browser, wherein a response header of the HTTP response message contains update identification information;
after receiving the HTTP response message, the browser judges whether the local update identification information is consistent with the update identification information in the response header, if not, the browser updates the local user related data and updates the local update identification information into the update identification information in the response header.
According to yet another aspect of the present application, there is also provided a browser device for updating local user-related data, wherein the device comprises:
the transmission module is used for sending an HTTP request message to the server and receiving an HTTP response message returned by the server, wherein a response header of the HTTP response message contains update identification information;
the judging module is used for judging whether the local update identification information is consistent with the update identification information in the response head;
and the updating module is used for updating the local user related data and updating the local updating identification information into the updating identification information in the response head if the local updating identification information is inconsistent with the updating identification information in the response head.
According to yet another aspect of the present application, there is also provided a computing device, wherein the device comprises a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method for updating user-related data local to a browser.
According to yet another aspect of the present application, there is also provided a computer readable medium having stored thereon computer program instructions executable by a processor to implement the method for updating user-related data local to a browser.
In the scheme provided by the application, the server returns an HTTP response message to the browser based on an HTTP request message sent by the browser, wherein a response header of the HTTP response message contains update identification information; the browser judges whether the local update identification information is consistent with the update identification information in the response head; if the update identification information of the local browser is inconsistent with the update identification information in the response header, updating the user related data of the local browser, and updating the update identification information of the local browser into the update identification information in the response header. According to the browser-side JS file updating method and device based on the B/S architecture, after the JS file at the browser side is updated, the local user-related data of the browser is automatically updated, the operation reliability is high, the efficiency is high, manual operation by a user is not needed, and therefore user experience is optimized.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the following drawings, in which:
FIG. 1 is a flow chart of a method for updating user-related data local to a browser according to an embodiment of the present application;
FIG. 2 is a flow chart of updating user-related data local to a browser according to an embodiment of the present application;
FIG. 3 is a flowchart of a method for updating local user-related data at a browser end according to an embodiment of the present application;
fig. 4 is a schematic diagram of a browser device for updating local user-related data according to an embodiment of the present application.
The same or similar reference numbers in the drawings refer to the same or similar parts.
Detailed Description
The present application is described in further detail below with reference to the accompanying drawings.
In one typical configuration of the present application, the terminal, the device of the service network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer-readable media include both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technology. The information may be computer readable instructions, data structures, program devices, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device.
The embodiment of the application provides a method for updating the local user related data of a browser based on a B/S architecture, after the JS file at the browser side is updated, the local user related data of the browser is automatically updated, the operation reliability is high, the efficiency is high, and manual operation by a user is not needed, so that the user experience is optimized.
In a practical scenario, the device implementing the method may be a user device, a network device, or a device formed by integrating the user device and the network device through a network. The user equipment comprises terminal equipment such as a smart phone, a tablet personal computer, a personal computer and the like, and the network equipment comprises network hosts, a single network server, a plurality of network server sets or a computer set based on cloud computing and the like. Here, the Cloud is composed of a large number of hosts or web servers based on Cloud Computing (Cloud Computing), which is a kind of distributed Computing, one virtual computer composed of a group of loosely coupled computer sets.
Fig. 1 is a flowchart of a method for updating user-related data local to a browser, the method including steps S101, S102, and S103, according to an embodiment of the present application.
Step S101, based on an HTTP request message sent by a browser, a server returns an HTTP response message to the browser, wherein a response header of the HTTP response message contains update identification information; step S102, the browser judges whether the local update identification information is consistent with the update identification information in the response head; step S103, if the update identification information of the local browser is inconsistent with the update identification information in the response header, updating the user related data of the local browser, and updating the update identification information of the local browser to the update identification information in the response header.
In some embodiments, the update identification information includes version number information. For example, the version number information contains a unique identification of the version of the software program, such as 1.0, 1.1, 1.2.1, 2.0, etc. As shown in fig. 2, the server may place version number information in the response header of the HTTP response message.
In some embodiments, the user-related data includes information of a user identity, a license, and the like. For example, at the browser side, the JS file version 1.0 stores encrypted user-related data: profile = confidence; version 2.0 JS file updates the data structure and adds new fields: profile= {1: confidence 1,2: confidence 2}; and the JS file version 3.0 may also make further modifications to the user-related data.
In some embodiments, the step S103 includes: if the corresponding update identification information does not exist in the local browser, namely the update identification information in the local browser is inconsistent with the update identification information in the response header, updating the user related data in the local browser, and writing the update identification information in the response header into the local browser.
For example, if the browser JS discovers that the local data does not have the corresponding version number information, the version number information in the response header is updated to the local data, the old user related data is cleared, and the new user related data is written.
In some embodiments, the step S103 includes: if the corresponding update identification information exists locally in the browser, but the update identification information in the local browser is inconsistent with the update identification information in the response header, updating the user related data in the local browser, and updating the update identification information in the local browser into the update identification information in the response header.
For example, the update identification information includes version number information, if the browser JS discovers that the corresponding version number information exists in the local data, but is inconsistent with the version number information in the response header, the version number information in the response header is updated to the local data, old user related data is removed, and new user related data is written.
In some embodiments, the method for updating user-related data local to a browser further comprises: if the corresponding update identification information exists locally in the browser and the update identification information locally in the browser is consistent with the update identification information in the response header, the operation of updating the user related data locally in the browser is not performed.
For example, if the browser side JS finds that the local data has the corresponding version number information and is consistent with the version number information in the response header, the update identification information includes version number information, which indicates that the access is not the first access after the JS version update at this time, and the user related data local to the browser side does not need to be updated.
Fig. 3 is a flowchart of a method applied to a browser end to update local user related data according to an embodiment of the present application, where the method includes step S301, step S302, and step S303.
Step S301, an HTTP request message is sent to a server, and an HTTP response message returned by the server is received, wherein a response header of the HTTP response message contains update identification information; step S302, judging whether the local update identification information is consistent with the update identification information in the response head; step S303, if the local update identification information is inconsistent with the update identification information in the response header, updating the local user related data, and updating the local update identification information as the update identification information in the response header.
In some embodiments, the update identification information includes version number information. For example, the version number information contains a unique identification of the version of the software program, such as 1.0, 1.1, 1.2.1, 2.0, etc. As shown in fig. 2, the server may place version number information in the response header of the HTTP response message.
In some embodiments, the user-related data includes information of a user identity, a license, and the like. For example, at the browser side, the JS file version 1.0 stores encrypted user-related data: profile = confidence; version 2.0 JS file updates the data structure and adds new fields: profile= {1: confidence 1,2: confidence 2}; and the JS file version 3.0 may also make further modifications to the user-related data.
In some embodiments, the step S303 includes: if the corresponding update identification information does not exist locally, namely the local update identification information is inconsistent with the update identification information in the response header, updating local user related data, and writing the update identification information in the response header into the local data.
For example, if the browser JS discovers that the local data does not have the corresponding version number information, the version number information in the response header is updated to the local data, the old user related data is cleared, and the new user related data is written.
In some embodiments, the step S303 includes: if the corresponding update identification information exists locally, but the local update identification information is inconsistent with the update identification information in the response header, updating the local user related data, and updating the local update identification information to the update identification information in the response header.
For example, the update identification information includes version number information, if the browser JS discovers that the corresponding version number information exists in the local data, but is inconsistent with the version number information in the response header, the version number information in the response header is updated to the local data, old user related data is removed, and new user related data is written.
In some embodiments, the method applied to the browser end for updating the local user related data further includes: if the corresponding update identification information exists locally and the local update identification information is consistent with the update identification information in the response header, the operation of updating the local user related data is not performed.
For example, if the browser side JS finds that the local data has the corresponding version number information and is consistent with the version number information in the response header, the update identification information includes version number information, which indicates that the access is not the first access after the JS version update at this time, and the user related data local to the browser side does not need to be updated.
Fig. 4 is a schematic diagram of a browser device for updating local user related data according to an embodiment of the present application, where the device includes a transmission module 401, a determination module 402, and an updating module 403.
The transmission module 401 is configured to send an HTTP request message to a server, and receive an HTTP response message returned by the server, where a response header of the HTTP response message includes update identification information; the judging module 402 is configured to judge whether the local update identification information is consistent with the update identification information in the response header; the update module 403 is configured to update local user related data if the local update identification information is inconsistent with the update identification information in the response header, and update the local update identification information to the update identification information in the response header.
In some embodiments, the update identification information includes version number information. For example, the version number information contains a unique identification of the version of the software program, such as 1.0, 1.1, 1.2.1, 2.0, etc. As shown in fig. 2, the server may place version number information in the response header of the HTTP response message.
In some embodiments, the user-related data includes information of a user identity, a license, and the like. For example, at the browser side, the JS file version 1.0 stores encrypted user-related data: profile = confidence; version 2.0 JS file updates the data structure and adds new fields: profile= {1: confidence 1,2: confidence 2}; and the JS file version 3.0 may also make further modifications to the user-related data.
In some embodiments, the update module 403 is configured to: if the corresponding update identification information does not exist locally, namely the local update identification information is inconsistent with the update identification information in the response header, updating local user related data, and writing the update identification information in the response header into the local data.
For example, if the browser JS discovers that the local data does not have the corresponding version number information, the version number information in the response header is updated to the local data, the old user related data is cleared, and the new user related data is written.
In some embodiments, the update module 403 is configured to: if the corresponding update identification information exists locally, but the local update identification information is inconsistent with the update identification information in the response header, updating the local user related data, and updating the local update identification information to the update identification information in the response header.
For example, the update identification information includes version number information, if the browser JS discovers that the corresponding version number information exists in the local data, but is inconsistent with the version number information in the response header, the version number information in the response header is updated to the local data, old user related data is removed, and new user related data is written.
In some embodiments, the browser device for updating local user-related data is further configured to: if the corresponding update identification information exists locally and the local update identification information is consistent with the update identification information in the response header, the operation of updating the local user related data is not performed.
For example, if the browser side JS finds that the local data has the corresponding version number information and is consistent with the version number information in the response header, the update identification information includes version number information, which indicates that the access is not the first access after the JS version update at this time, and the user related data local to the browser side does not need to be updated.
According to another aspect of the present application, there is also provided a system for updating user-related data local to a browser, wherein the system includes a browser and a server;
the server returns an HTTP response message to the browser based on the HTTP request message sent by the browser, wherein a response header of the HTTP response message contains update identification information;
after receiving the HTTP response message, the browser judges whether the local update identification information is consistent with the update identification information in the response header, if not, the browser updates the local user related data and updates the local update identification information into the update identification information in the response header.
In some embodiments, the update identification information includes version number information. For example, the version number information contains a unique identification of the version of the software program, such as 1.0, 1.1, 1.2.1, 2.0, etc. As shown in fig. 2, the server may place version number information in the response header of the HTTP response message.
In some embodiments, the user-related data includes information of a user identity, a license, and the like. For example, at the browser side, the JS file version 1.0 stores encrypted user-related data: profile = confidence; version 2.0 JS file updates the data structure and adds new fields: profile= {1: confidence 1,2: confidence 2}; and the JS file version 3.0 may also make further modifications to the user-related data.
In some embodiments, if the corresponding update identification information does not exist locally in the browser, that is, the update identification information locally in the browser is inconsistent with the update identification information in the response header, the user-related data locally in the browser is updated, and the update identification information in the response header is written locally in the browser.
For example, if the browser JS discovers that the local data does not have the corresponding version number information, the version number information in the response header is updated to the local data, the old user related data is cleared, and the new user related data is written.
In some embodiments, if the corresponding update identification information exists locally to the browser, but the update identification information locally to the browser is inconsistent with the update identification information in the response header, the user-related data locally to the browser is updated, and the update identification information locally to the browser is updated to the update identification information in the response header.
For example, the update identification information includes version number information, if the browser JS discovers that the corresponding version number information exists in the local data, but is inconsistent with the version number information in the response header, the version number information in the response header is updated to the local data, old user related data is removed, and new user related data is written.
In some embodiments, if the corresponding update identification information exists locally in the browser, and the update identification information locally in the browser is consistent with the update identification information in the response header, the operation of updating the user-related data locally in the browser is not performed.
For example, if the browser side JS finds that the local data has the corresponding version number information and is consistent with the version number information in the response header, the update identification information includes version number information, which indicates that the access is not the first access after the JS version update at this time, and the user related data local to the browser side does not need to be updated.
In summary, the embodiment of the application automatically updates the local user related data of the browser based on the B/S architecture after the JS file at the browser side is updated, so that the operation reliability is high, the efficiency is high, and the manual operation of the user is not required, thereby optimizing the user experience.
Furthermore, portions of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application by way of operation of the computer. Program instructions for invoking the methods of the present application may be stored in fixed or removable recording media and/or transmitted via a data stream in a broadcast or other signal bearing medium and/or stored within a working memory of a computer device operating according to the program instructions. Some embodiments of the present application provide a computing device comprising a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the methods and/or aspects of the various embodiments of the present application described previously.
Furthermore, some embodiments of the present application provide a computer readable medium having stored thereon computer program instructions executable by a processor to implement the methods and/or aspects of the various embodiments of the present application described above.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, using Application Specific Integrated Circuits (ASIC), a general purpose computer or any other similar hardware device. In some embodiments, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs of the present application (including associated data structures) may be stored on a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. In addition, some steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units or means recited in the apparatus claims can also be implemented by means of one unit or means in software or hardware. The terms first, second, etc. are used to denote a name, but not any particular order.

Claims (10)

1. A method for updating user-related data local to a browser, wherein the method comprises:
based on an HTTP request message sent by a browser, a server returns an HTTP response message to the browser, wherein a response header of the HTTP response message contains update identification information;
the browser judges whether the local update identification information is consistent with the update identification information in the response head;
if the update identification information of the local browser is inconsistent with the update identification information in the response header, updating the user related data of the local browser, and updating the update identification information of the local browser into the update identification information in the response header.
2. The method of claim 1, wherein if the browser-local update identification information does not coincide with the update identification information in the response header, updating the browser-local user-related data and updating the browser-local update identification information to the update identification information in the response header comprises:
if the corresponding update identification information does not exist in the local browser, namely the update identification information in the local browser is inconsistent with the update identification information in the response header, updating the user related data in the local browser, and writing the update identification information in the response header into the local browser.
3. The method of claim 1, wherein if the browser-local update identification information does not coincide with the update identification information in the response header, updating the browser-local user-related data and updating the browser-local update identification information to the update identification information in the response header comprises:
if the corresponding update identification information exists locally in the browser, but the update identification information in the local browser is inconsistent with the update identification information in the response header, updating the user related data in the local browser, and updating the update identification information in the local browser into the update identification information in the response header.
4. The method of claim 1, wherein the method further comprises:
if the corresponding update identification information exists locally in the browser and the update identification information locally in the browser is consistent with the update identification information in the response header, the operation of updating the user related data locally in the browser is not performed.
5. The method of any of claims 1 to 4, wherein the update identification information includes version number information.
6. A method for updating local user-related data applied to a browser, wherein the method comprises:
an HTTP request message is sent to a server, and an HTTP response message returned by the server is received, wherein a response header of the HTTP response message contains update identification information;
judging whether the local update identification information is consistent with the update identification information in the response head;
if the local updating identification information is inconsistent with the updating identification information in the response head, updating the local user related data, and updating the local updating identification information into the updating identification information in the response head.
7. A system for updating user-related data local to a browser, wherein the system comprises a browser and a server;
the server returns an HTTP response message to the browser based on the HTTP request message sent by the browser, wherein a response header of the HTTP response message contains update identification information;
after receiving the HTTP response message, the browser judges whether the local update identification information is consistent with the update identification information in the response header, if not, the browser updates the local user related data and updates the local update identification information into the update identification information in the response header.
8. A browser device for updating local user-related data, wherein the device comprises:
the transmission module is used for sending an HTTP request message to the server and receiving an HTTP response message returned by the server, wherein a response header of the HTTP response message contains update identification information;
the judging module is used for judging whether the local update identification information is consistent with the update identification information in the response head;
and the updating module is used for updating the local user related data and updating the local updating identification information into the updating identification information in the response head if the local updating identification information is inconsistent with the updating identification information in the response head.
9. A computing device, wherein the device comprises a memory for storing computer program instructions and a processor for executing the computer program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of any one of claims 1 to 6.
10. A computer readable medium having stored thereon computer program instructions executable by a processor to implement the method of any of claims 1 to 6.
CN202310210447.0A 2023-03-06 2023-03-06 Method, device and system for updating user-related data local to browser Pending CN116248502A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202310210447.0A CN116248502A (en) 2023-03-06 2023-03-06 Method, device and system for updating user-related data local to browser

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202310210447.0A CN116248502A (en) 2023-03-06 2023-03-06 Method, device and system for updating user-related data local to browser

Publications (1)

Publication Number Publication Date
CN116248502A true CN116248502A (en) 2023-06-09

Family

ID=86632909

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202310210447.0A Pending CN116248502A (en) 2023-03-06 2023-03-06 Method, device and system for updating user-related data local to browser

Country Status (1)

Country Link
CN (1) CN116248502A (en)

Similar Documents

Publication Publication Date Title
US9047224B2 (en) Method, system and server of removing a distributed caching object
US10356156B2 (en) Method and device for loading webpage
WO2020181810A1 (en) Data processing method and apparatus applied to multi-level caching in cluster
CN107153644B (en) Data synchronization method and device
CN110362547B (en) Method and device for encoding, analyzing and storing log file
CN107733882B (en) SSL certificate automatic deployment method and equipment
CN106528578A (en) An information display method and device
CN111324665A (en) Log playback method and device
US20120265831A1 (en) System and Method for Transmitting and Filtering Instant Messaging Information
CN111104232A (en) Method, device and medium for accelerating message writing of message queue
CN110049133B (en) Method and device for issuing full amount of DNS zone files
US8725765B2 (en) Hierarchical registry federation
CN116248502A (en) Method, device and system for updating user-related data local to browser
CN112860746B (en) Cache reduction-based method, equipment and system
CN111600943B (en) Method and equipment for acquiring target data
CN112434233B (en) Method and device for accelerating first screen rendering of secondary page
CN112765129A (en) Method and equipment for realizing database data version management
CN112395591A (en) Encryption method and system
CN113157261B (en) Code generation method and device
CN113660172B (en) Flow control method and device
CN110677919B (en) Method and equipment for sharing and determining income based on wireless access point
CN111639936B (en) Transaction information acquisition method and device, electronic equipment and readable storage medium
CN112383415A (en) Server side marking method and equipment
CN114065079A (en) Method and equipment for generating PDF file by Web
CN113608803A (en) Method and equipment for realizing functional operation in multi-operation environment

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