CN103198142B - Page data renewal processing method, client and server - Google Patents

Abstract

An embodiment of the present invention provides a page data update processing method, a client and a server. The method includes: receiving a first operation request sent from an operation interface on the client, and performing operations in the buffer space according to the first page update information. The page corresponding to the interface identifier is updated. Since each operation interface has a unique identifier indicating the operation interface, the client will update the intermediate data generated in each step during the paging and step-by-step operation of the maintenance object. The information is cached in the shared cache space with the identifier of the operation interface. The data of each operation interface in the cache space is independent of each other. Even if the client operates on the same maintenance object through different operation interfaces, the problem of data coverage will not occur.

Description

Page data update processing method, client and server

technical field

The invention relates to the technical field of network communication, in particular to a method for updating page data, a client and a server.

Background technique

In the WEB application system, the information maintainer can access and maintain the server through the IE browser of the client, display pages through different tabs or different windows of the browser, and use the mechanism of intermediate data caching for business maintenance.

In the prior art, generally, the ID of the object to be maintained (Identity, hereinafter referred to as ID) is used to operate the session layer, that is, the ID of the maintenance object in all opened windows or tabs is stored in the session layer, and through the stored ID to confirm the maintenance object, when you click "Back" or "Next" on the page of different tabs or different windows, find the corresponding maintenance object in the session layer according to the ID for update and maintenance, etc.

However, when there is a lot of information to be maintained on different pages, in the process of information maintenance, especially in the process of modification and other operations, two windows or tabs will be opened for the same maintenance object at the same time for comparison. At this time, If the user irregularly clicks pages of different tabs or windows, different windows or tabs of the browser have the feature of sharing the session layer, which may easily cause data coverage problems.

Contents of the invention

Embodiments of the present invention provide a page data update processing method, client and server to solve the problem of data coverage caused by different windows or different tabs of the browser due to the shared session layer during the data update process.

In the first aspect, the embodiment of the present invention provides a data update processing method, including:

receiving a first operation request sent from an operation interface on the client, where the first operation request includes update information on the first page on the operation interface and an identifier of the operation interface;

According to the first page update information, update processing is performed on the page corresponding to the identifier of the operation interface in the cache space.

In a first possible implementation manner of the first aspect, after updating the page corresponding to the identifier of the operation interface in the cache space according to the first page update information, the method further includes:

Sending a first operation response to the client, where the first operation response includes the identifier of the operation interface.

With reference to the first aspect or the first possible implementation of the first aspect, in the second possible implementation, before receiving the first operation request sent from the operation interface on the client, it further includes:

receiving a second operation request sent from the operation interface on the client, the second operation request indicating that the operation interface needs to be updated; generating an identifier of the operation interface; returning a second operation response to the client , the second operation response carries the identifier of the window interface.

With reference to the second possible implementation of the first aspect, in a third possible implementation, the generating the identifier of the operation interface includes: generating the operation interface according to the opening time of the operation interface or, randomly generate the identifier of the operation interface.

With reference to the first, second or third possible implementation of the first aspect, in a fourth possible implementation, the identifier of the operation interface is carried in the operation response in the form of a hidden field .

In combination with the first aspect, any one of the first to fourth possible implementations of the first aspect, in the fifth possible implementation, according to the first page The update information, after updating the page corresponding to the identifier of the operation interface in the cache space, further includes:

According to a preset strategy, clear the logo of the operation interface; or,

Receiving an update processing end request sent from the operation interface on the client, and clearing the identifier of the operation interface.

With reference to the fifth possible implementation manner of the first aspect, in a sixth possible implementation manner, the clearing the identifier of the operation interface according to a preset strategy includes:

The identifiers of the operation interface are cleared according to a timing cleaning strategy or a strategy of limiting the maximum number of identifiers.

With reference to the first aspect, any one of the first to sixth possible implementations of the first aspect, in a seventh possible implementation, the operation interface is a browser window or tab.

In combination with the first aspect, any one of the first to seventh possible implementations of the first aspect, in an eighth possible implementation, the cache space is a session layer, Cookies or distributed memory object caching systems.

In the second aspect, the embodiment of the present invention provides a page data update processing method, including:

Sending a first operation request to the server through the operation interface, the first operation request including the first page update information on the operation interface and the identifier of the operation interface;

receiving a first operation response sent by the server, where the first operation response includes the identifier of the operation interface;

Analyzing the identifier of the operation interface from the first operation response.

In a first possible implementation manner of the second aspect, the first operation request is sent to the server through the operation interface, and the first operation request includes the first page update information on the operation interface and the Before the identification of the operation interface, it also includes:

sending a second operation request to the server through the operation interface, where the second operation request needs to update the operation interface;

and receiving a second operation response sent by the server, where the second operation response carries the identifier of the window interface.

In a third aspect, an embodiment of the present invention provides a server, including:

A receiving module, configured to receive a first operation request sent from an operation interface on the client, where the first operation request includes update information on the first page on the operation interface and an identifier of the operation interface;

A processing module, configured to update the page corresponding to the identifier of the operation interface in the cache space according to the first page update information.

In a first possible implementation manner of the third aspect, the server further includes:

A first sending module, configured to send a first operation response to the client, where the first operation response includes the identifier of the operation interface.

In combination with the third aspect or the first possible implementation of the third aspect, in a second possible implementation, the receiving module is further configured to:

receiving a second operation request sent from the operation interface on the client, the second operation request indicating that the operation interface needs to be updated;

The processing module is also used to generate an identifier of the operation interface;

The server further includes a second sending module, configured to return a second operation response to the client, where the second operation response carries the identifier of the window interface.

In combination with the second possible implementation of the third aspect, in the third possible implementation, the processing module is specifically configured to:

Generate an identifier of the operation interface according to the opening time of the operation interface; or,

The identifier of the operation interface is randomly generated.

With reference to the first, second or third possible implementation of the third aspect, in a fourth possible implementation, the identifier of the operation interface is carried in the operation response in the form of a hidden field .

With reference to the third aspect, any possible implementation manner in the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation manner, the server further includes:

A clearing module, configured to clear the identifier of the operation interface according to a preset strategy; or,

When the receiving module receives an update processing end request sent from the operation interface on the client, it clears the identifier of the operation interface.

With reference to the fifth possible implementation of the third aspect, in a sixth possible implementation, the clearing module is specifically configured to:

The identifiers of the operation interface are cleared according to a timing cleaning strategy or a strategy of limiting the maximum number of identifiers.

With reference to the third aspect, any one of the first to sixth possible implementations of the third aspect, in a seventh possible implementation, the operation interface is a browser window or tab.

In combination with the third aspect, any possible implementation manner of the first to the seventh possible implementation manners of the third aspect, in an eighth possible implementation manner, the cache space is a session layer, Cookies or distributed memory object caching systems.

In a fourth aspect, an embodiment of the present invention provides a client, including:

A sending module, configured to send a first operation request to the server through the operation interface, where the first operation request includes the first page update information on the operation interface and the identifier of the operation interface;

A receiving module, configured to receive a first operation response sent by the server, where the first operation response includes the identifier of the operation interface;

A parsing module, configured to parse out the identifier of the operation interface from the first operation response.

In a first possible implementation manner of the fourth aspect, the sending module is further configured to:

sending a second operation request to the server through the operation interface, where the second operation request needs to update the operation interface;

The receiving module is further configured to receive a second operation response sent by the server, where the second operation response carries the identifier of the window interface.

An embodiment of the present invention provides a page data update processing method, a client and a server, and the server receives the first operation request sent from the operation interface on the client and includes the first page update information on the operation interface and the identifier of the operation interface , according to the first page update information, update the page corresponding to the identifier of the operation interface in the cache space. In the embodiment of the present invention, since each operation interface has a unique identifier indicating the operation interface, when there are many maintenance objects in the operation interface, further, each maintenance object can use the identifier of the operation interface and the maintenance object. The combined unique indication of the identity of the object enables the client to cache the intermediate information generated in each step in the shared cache space by using the identifier of the operation interface as the identifier during the paging and step-by-step operation of maintaining the object. The data of each operation interface in the space is independent of each other, even if the client operates on the same maintenance object through different operation interfaces, the problem of data coverage will not occur.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

FIG. 1 is a flow chart of Embodiment 1 of the page data update processing method of the present invention;

FIG. 2 is a flow chart of Embodiment 2 of the page data update processing method of the present invention;

FIG. 3 is a signaling diagram of Embodiment 3 of the page data update processing method of the present invention;

FIG. 4 is a schematic structural diagram of Embodiment 1 of the server of the present invention;

FIG. 5 is a schematic structural diagram of the second embodiment of the server of the present invention;

FIG. 6 is a schematic structural diagram of the client of the present invention.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments It is a part of embodiments of the present invention, but not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

FIG. 1 is a flow chart of Embodiment 1 of the page data update processing method of the present invention, and the execution subject of this embodiment is a server. Specifically, this embodiment includes the following steps:

101. Receive a first operation request sent from an operation interface on a client, where the first operation request includes first page update information on the operation interface and an identifier of the operation interface.

The operation interface on the client is generally presented in the form of tabs or browser windows, each tab or browser window can have one or more maintenance objects, and for each maintenance object, there can be a Multiple pages, each page has command buttons such as "Add", "Delete", "Modify" or "Save" for users to operate; or "Previous" or "Next" for users to select different pages Page" and other selection buttons. Taking the operation interface of IE8 as an example, if the operation interface is in the browser window display mode, each time a webpage is opened, the webpage will be opened and displayed in a new window; otherwise, if the operation interface is in the tab display mode, each time a webpage is opened, Then create a tab, and open and display the web page in the newly created tab. In this step, the client sends the first operation request to the server after updating the first page of the operation interface. After the update process, the client is instructed to update the first page of the operation interface, and the server receives the first operation request including the update information of the first page on the operation interface and the identifier of the operation interface. Specifically, if the client updates the first pages of different operation interfaces, each operation interface sends to the server the update information of the first page carrying the corresponding operation interface and the identification of the corresponding operation interface (tab identification or browser window ID) for the first action request.

102. Perform update processing on the page corresponding to the identifier of the operation interface in the cache space according to the first page update information.

The cache space is the built-in cache mechanism of the server, such as the session layer (session), the distributed memory object cache system (memCached) or the information recording program (Cookie) of the IE browser, etc., and the present invention is not limited thereto. When the server receives the update information of the first page carrying the identifier of the operation interface sent by the client, it determines the information of the page corresponding to the identifier in the cache space according to the identifier of the operation interface and performs update processing, that is, the temporarily stored original The page information of is updated to the first page update information. Generally speaking, if there is only one maintenance object in the operation interface or it is relatively fixed, then directly determine the operation interface corresponding to the identifier from the cache space according to the identifier of the operation interface and update it; otherwise, if the If there are many maintenance objects, after the operation interface corresponding to the identification is determined from the cache space according to the identification of the operation interface, the specific maintenance object can be determined according to the identity identification of the maintenance object, and then the maintenance object can be updated. That is, in this step, each operation interface has a unique identifier indicating the operation interface; when there are many maintenance objects in the operation interface, further, each maintenance object can use the identifier of the operation interface and the maintenance object. The unique indication of the object's identity.

In the page data update processing method provided by the embodiment of the present invention, the server receives the first operation request sent from the operation interface on the client and includes the first page update information on the operation interface and the identification of the operation interface, and updates the first page according to the first operation request. information, and update the page corresponding to the identifier of the operation interface in the cache space. In the embodiment of the present invention, since each operation interface has a unique identifier indicating the operation interface, when there are many maintenance objects in the operation interface, further, each maintenance object can use the identifier of the operation interface and the maintenance object. The combined unique indication of the identity of the object enables the client to cache the intermediate information generated in each step in the shared cache space by using the identifier of the operation interface as the identifier during the paging and step-by-step operation of maintaining the object. The data of each operation interface in the space is independent of each other, even if the client operates on the same maintenance object through different operation interfaces, the problem of data coverage will not occur.

In the first embodiment above, after updating the page corresponding to the identifier of the operation interface in the cache space according to the first page update information, the server may return the first operation response to the client according to the specific form of the first operation request , the first operation response contains the identifier of the operation interface.

Specifically, if the first operation request is triggered after the client updates the first page of the maintenance object in the operation interface, click "Next" to enter the next page to update the information on the second page of the maintenance object That is, it is triggered by clicking "Next", then the server obtains the latest original page information of the second page at this time, and sends the identifier of the operation interface to the client in the original page information of the second page, so that The client parses out the identifier of the operation interface to determine the operation interface, displays the original page information of the second page on the determined operation interface, and performs update processing.

If the first operation request is triggered by clicking "Save" after the client updates the first page of the maintenance object in the operation interface, then the server will cache the updated page information of the maintenance object in the cache space Update to the database, and send the identifier of the operation interface to the client in the first operation response of successful update processing.

Further, in the first embodiment above, before the server receives the first operation request sent from the operation interface on the client, it needs to generate an operation interface identifier for each operation interface that initiates the first operation request. Specifically, the server receives the second operation request sent from the operation interface on the client, and the second operation request indicates that the window interface needs to be updated; generates the identifier of the operation interface, and returns the second operation response to the client, and the second operation The response carries the identifier of the window interface.

Generally speaking, after the client opens the operation interface for the first time, if the maintenance object in the operation interface is unique or the number is relatively small, it will send a second operation request to the server through the operation interface, requesting to update the user interface ; If there are many maintenance objects in the operation interface, select the object to be updated and then send the second operation request to the server through the operation interface. A maintenance object for update processing.

After receiving the second operation request, the server finds that the operation interface does not have a corresponding identifier, and generates an identifier of the operation interface for the operation interface. Specifically, since the opening of each operation interface takes time, so that the opening time of each operation interface is different, the server can generate the identifier of the operation interface according to the opening time of the operation interface; or randomly generate the identifier of the operation interface For identification, for example, timestamps, random numbers, etc. can be used to generate the identification of the operation interface, and the algorithm for the identification of the operation interface only needs to ensure uniqueness.

Further, since the identifier of the operation interface is only used to identify the operation interface, it has no specific business meaning. Therefore, the identifier of the operation interface is generally carried in the operation response in the form of a hidden field, for example, the identifier of the operation interface is set as a hidden field and then carried in the above-mentioned first operation response or second operation response and sent to the client. Specifically, the identifier of the operation interface can be flexibly selected as a hidden field or not set according to business needs.

Further, in order to prevent data congestion caused by too many combinations of the identifier of the operation interface in the shared cache space, or the identifier indicating the operation interface of the maintenance object and the identity identifier of the maintenance object, the server updates the information according to the first page, and updates the cache After the page corresponding to the logo of the operation interface in the space is updated, the logo of the operation interface can also be cleared according to the preset strategy, according to the timing cleaning strategy or the strategy of limiting the maximum number of logos, for example, timing or event-triggered or set a reference duration, if the operation interface identifier or the combination of the operation interface identifier and the identity identifier of the maintenance object in the cache space exceeds the reference duration, it will be actively cleared; Alternatively, the server may clear the identifier of the operation interface after receiving the update end request sent by the information maintainer through the operation interface on the client. For example, in the first embodiment above, when the information maintainer clicks "Save" to send the first The operation request causes the server to clear the identifier of the operation interface or the combination of the identifier of the operation interface and the identity identifier of the maintenance object in the cache space after updating the updated page information of the maintenance object in the cache space to the database.

Taking the maintenance objects in the operation interface as multiple books as an example, after selecting the book that needs to be updated, the time point when the operation interface is opened is used as the identification of the operation interface, and the combination of the identification of the operation interface and the identity of the book is used as the identification of the operation interface. The logo of the book, if the logo is defined as "key", then in the JAVA language, the server can obtain the key in the following way, String key=System.currentTimeMillis()+"_"+bookid; when the server returns an operation response to the client , set the key as a hidden field, and implement the following code on the server web page (Java Server Page, hereinafter referred to as JSP):

<form action="xxxx">

<input type="hidden" name="key" value="<%key%>">

<input type="text" name="bookName" value="<%bookName%>">

...

＜/form＞

FIG. 2 is a flow chart of Embodiment 2 of the page data update processing method of the present invention, and the execution subject of this embodiment is a client. Specifically, this embodiment includes the following steps:

201. Send a first operation request to the server through the operation interface, where the first operation request includes update information of the first page on the operation interface and an identifier of the operation interface.

The client operates on different operation interfaces, and sends a first operation request carrying update information of the first page of the corresponding operation interface and an identifier of the corresponding operation interface to the server through each operation interface.

202. Receive a first operation response sent by the server, where the first operation response includes an identifier of the operation interface.

After responding to the first operation request, the server sends a first operation response to the client, and the server receives the first operation response including the identifier of the operation interface.

203. Parse the identifier of the operation interface from the first operation response.

There may be multiple operation interfaces opened by the client. Therefore, after the client receives the first operation response sent by the server, it parses the first operation response, parses out the identifier of the operation interface, determines the specific operation interface according to the identifier of the parsed operation interface, and sends the second The response information of an operation response is displayed on the determined operation interface for the information maintainer to operate. For example, if the first operation request is triggered after the client updates the first page of the maintenance object in the operation interface, click "Next" to enter the next page to update and process the information on the second page of the maintenance object , the first operation response carries the original page information on the second page, then the client displays the information on the second page on the operation interface for the client to update and process; if the first operation request is on the client’s operation interface After the first page of the maintenance object is updated, click "Save" to trigger, then the first operation response is a response message that the information update process is successful, and at this time, the client can end the update maintenance of the operation interface.

In the page data update processing method provided by the embodiment of the present invention, the operation interface on the client sends to the server a first operation request including the first page update information on the operation interface and the identification of the operation interface, so that the server uses the first page update information, and update the page corresponding to the identifier of the operation interface in the cache space. In the embodiment of the present invention, since each operation interface has a unique identifier indicating the operation interface, when there are many maintenance objects in the operation interface, further, each maintenance object can use the identifier of the operation interface and the maintenance object. The combination of the object's identity uniquely indicates that the client caches the intermediate information generated in each step in the shared cache space with the identifier of the operation interface during the paging and step-by-step operation of maintaining the object. The data of each operation interface in the system is independent of each other, even if the information maintenance personnel operate the same maintenance object through different operation interfaces, the problem of data coverage will not occur.

Further, in the second embodiment above, the client sends the first operation request to the server through the operation interface, and before the first operation request includes the update information of the first page on the operation interface and the identification of the operation interface, it needs to request from the server A corresponding operation interface identifier is generated for the operation interface, so that the identifier of the operation interface can be directly used in the subsequent page data update process. Specifically, the client sends a second operation request to the server through the operation interface, and the second operation request indicates that the operation interface needs to be updated; receives the second operation response sent by the server, and the second operation response carries the identifier of the window interface.

Generally speaking, after the client opens the operation interface for the first time, if the maintenance object in the operation interface is unique or the number is relatively small, it will send a second operation request to the server through the operation interface, requesting to update the user interface ; If there are many maintenance objects in the operation interface, select the object to be maintained and then send a second operation request to the server through the operation interface. At this time, updating the user interface specifically refers to a certain Maintain objects for update processing. After receiving the second operation request, the server finds that the operation interface does not have a corresponding identifier, generates an identifier of the operation interface for the operation interface, and sends the identifier of the operation interface to the client in the second operation response, The client receives the second operation response.

Figure 3 is a signaling diagram of Embodiment 3 of the page data update processing method of the present invention. In this embodiment, the user interface is specifically a browser window and includes multiple maintenance objects, and the cache space is specifically a session layer (session). For the same The maintenance object opens two windows for page data update processing as an example to elaborate on the technical solution of the present invention. For the sake of clarity, one of the two opened windows is called the modification window, and the window is identified as A, and the other is called It is the reference window, and the window is identified as B. Specifically, this embodiment includes the following steps:

301. The information maintainer opens the modification window, selects the object to be updated and clicks modification;

302. Send a second operation request to the server through the modification window, requesting that the first page of the modification window needs to be updated, specifically updating the first page of the maintenance object selected in the modification window.

303. The server obtains the latest page information of the first page from the database.

304. The server generates an identifier A for the modification window, and stores the window identifier A, the latest page information of the first page, and the corresponding relationship in the Session.

305. The server sends a second operation response to the client, where the operation response carries the latest page information of the first page and the identifier A of the modification window.

306. The client displays the information of the first page in the modification window according to the latest page information of the first page.

307. The information maintainer opens the reference window, selects the same maintenance object as in 301, and clicks "modify".

308. Send a second operation request to the server through the reference window, requesting that the first page of the reference window needs to be updated, specifically update the first page of the selected maintenance object in the reference window.

309. The server obtains the latest page information of the first page from the database.

310. The server generates an identifier B for the reference window, and stores the window identifier B, the latest page information of the first page, and the corresponding relationship in the Session.

311. The server sends a second operation response to the client, where the operation response carries the latest page information of the first page and the identifier B of the reference window.

312. The client displays the first page information in the reference window according to the latest page information of the first page.

313. After the information maintainer modifies and updates the first page of the modification window, he clicks "Next" to enter the next page.

314. The client sends a first operation request to the server by modifying the window, where the first operation request carries the identifier A of the modification window.

315. The server determines the modification window according to the identifier A in the first operation request, updates the information of the modification window temporarily stored in the Session, and obtains the latest page information of the second page from the database.

During the update process, the server determines according to the identifier A that the information maintainer has updated the modification window. Specifically, which maintenance object in the modification window can be determined according to the identity ID of the maintenance object. Specifically, it can be Refer to the prior art, which will not be repeated here.

316. The server sends a first operation response to the client, where the first operation response carries the identifier A of the modification window and the latest page information of the second page.

317. After receiving the first operation response, the client parses out the window identifier A, determines that it is a modification window, and displays the latest information on the second page in the modification window.

318. The information maintainer clicks "Next" in the reference window to enter the next page of the reference window.

Optionally, in this step, the information maintainer may also update the reference window by modifying it.

319. The client sends a first operation request to the server through the reference window, where the first operation request carries the identifier B of the reference window.

320. The server determines the reference window according to the identifier B in the first operation request, updates the first page of the reference window temporarily stored in the Session, and obtains the latest page information of the second page from the database.

321. The server sends a first operation response to the client, where the first operation response carries the identifier B of the reference window and the latest page information of the second page.

322. After receiving the first operation response, the client parses out the window identifier B, determines that it is the reference window, and displays the latest information on the second page in the reference window.

323. The information maintainer clicks "Save" after performing update processing such as modification on the second page of the modification window.

It should be noted that each maintenance object may have multiple pages storing the information of the maintenance object. In this step, the second page is only updated as an example to illustrate the present invention in detail. However, in actual operation, the information The maintainer can maintain each page, or click "previous page" and "next page" irregularly to switch between different pages, update all pages and click "save".

324. The client sends an update processing end request to the server through the modification window, where the update processing end request carries the identifier A of the modification window.

325. The server receives the update processing end request, determines the modification window according to the identifier A, and updates the information of the corresponding modification window in the Session.

326. The server updates the information of all pages of the modified window A cached in the updated Session to the database.

327. The server returns a successful instruction to the client, and the successful instruction carries the identifier A of the modification window.

328. After receiving the successful instruction, the client parses out the identifier A, determines that it is a modification window, and then displays information that the update process is successful in the modification window.

It should be noted that after the above step 326, the server can also temporarily store the identifier of the modification window in the Session, the combination of the identifier of the modification window and the identity identifier of the maintenance object, and related information, such as the first page and the second page Or, during the page data update process, when the modification window has not been operated for more than a certain period of time, the information related to the modification window in the Session can be actively cleared.

FIG. 4 is a schematic structural diagram of Embodiment 1 of the server of the present invention. As shown in FIG. 4 , the server provided in this embodiment can specifically implement each step of the method applied to the server provided in any embodiment of the present invention, and the specific implementation process will not be repeated here. The server provided in this embodiment specifically includes:

The receiving module 11 is configured to receive the first operation request sent from the operation interface on the client, the first operation request includes the first page update information on the operation interface and the identification of the operation interface, and optionally, the operation interface is browsing browser window or tab;

The processing module 12 is configured to update the page corresponding to the identifier of the operation interface in the cache space according to the update information of the first page. Optionally, the cache space is a session layer, an information recording program or a distributed memory object cache system.

In the server provided by the embodiment of the present invention, the server receives the first operation request sent from the operation interface on the client and includes the first page update information on the operation interface and the identification of the operation interface, and according to the first page update information, cache The page corresponding to the identifier of the operation interface in the space is updated. In the embodiment of the present invention, since each operation interface has a unique identifier indicating the operation interface, when there are many maintenance objects in the operation interface, further, each maintenance object can use the identifier of the operation interface and the maintenance object. The combined unique indication of the identity of the object enables the client to cache the intermediate information generated in each step in the shared cache space by using the identifier of the operation interface as the identifier during the paging and step-by-step operation of maintaining the object. The data of each operation interface in the space is independent of each other, even if the client operates on the same maintenance object through different operation interfaces, the problem of data coverage will not occur.

Fig. 5 is a schematic structural diagram of the second embodiment of the server of the present invention. As shown in Fig. 5, the server of this embodiment may further include:

The first sending module 13 is configured to send a first operation response to the client, where the first operation response includes the identifier of the operation interface.

Further, the receiving module 11 is also configured to receive a second operation request sent from the operation interface on the client, and the second operation request indicates that the operation interface needs to be updated;

The processing module 12 is also used to generate the identification of the operation interface;

Further, please refer to FIG. 4 again, the server provided in this embodiment further includes a second sending module 14, configured to return a second operation response to the client, and the second operation response carries the identifier of the window interface.

Further, the processing module 12 is specifically configured to: generate an operation interface identifier according to the opening time of the operation interface; or randomly generate an operation interface identifier.

Further, the identifier of the operation interface is carried in the operation response in the form of a hidden field.

Further, referring to FIG. 4 again, the server provided in this embodiment also includes:

The clearing module 15 is configured to clear the identifier of the operation interface according to a preset strategy; or, when the receiving module 11 receives an update processing end request from the operation interface on the client, clear the identifier of the operation interface.

Further, the clearing module 15 is specifically configured to clear the identifiers of the operation interface according to the timing clearing strategy or the maximum identifier limit strategy.

FIG. 6 is a schematic structural diagram of the client of the present invention. As shown in FIG. 6 , the client provided by this embodiment can specifically implement each step of the method applied to the client provided by any embodiment of the present invention, and the specific implementation process will not be repeated here. The clients provided in this embodiment specifically include:

The sending module 21 is configured to send a first operation request to the server through the operation interface, where the first operation request includes the first page update information on the operation interface and the identifier of the operation interface;

The receiving module 22 is configured to receive the first operation response sent by the server, and the first operation response includes the identifier of the operation interface;

The parsing module 23 is configured to parse out the identifier of the operation interface from the first operation response.

In the client provided by the embodiment of the present invention, by sending the first operation request including the first page update information on the operation interface and the identification of the operation interface to the server, the server uses the first page update information to perform operations in the cache space. The page corresponding to the identifier of the interface is updated. In the embodiment of the present invention, since each operation interface has a unique identifier indicating the operation interface, when there are many maintenance objects in the operation interface, further, each maintenance object can use the identifier of the operation interface and the maintenance object. The combination of the object's identity uniquely indicates that the client caches the intermediate information generated in each step in the shared cache space with the identifier of the operation interface during the paging and step-by-step operation of maintaining the object. The data of each operation interface in the system is independent of each other, even if the information maintenance personnel operate the same maintenance object through different operation interfaces, the problem of data coverage will not occur.

Further, the sending module 21 is also used to: send a second operation request to the server through the operation interface, and the second operation request needs to update the operation interface;

The receiving module 22 is also configured to receive the second operation response sent by the server, and the second operation response carries the identifier of the window interface.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than limiting them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: It is still possible to modify the technical solutions described in the foregoing embodiments, or perform equivalent replacements for some or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the technical solutions of the various embodiments of the present invention. scope.

Claims (22)

1. A page data updating processing method is characterized by comprising the following steps:

receiving a first operation request sent by an operation interface on a client, wherein the first operation request comprises first page update information on the operation interface and an identifier of the operation interface, and the first operation request is sent after the client updates the first page of the operation interface;

and updating the page corresponding to the identifier of the operation interface in the cache space according to the first page update information so as to update the original page information of the page corresponding to the identifier of the operation interface into the first page update information.

2. The method according to claim 1, wherein after the updating the page corresponding to the identifier of the operation interface in the cache space according to the first page update information, the method further includes:

and sending a first operation response to the client, wherein the first operation response comprises the identification of the operation interface.

3. The method according to claim 1 or 2, wherein before receiving the first operation request sent from the operation interface on the client, the method further comprises:

receiving a second operation request sent by an operation interface on the client, wherein the second operation request indicates that the operation interface needs to be updated;

generating an identifier of the operation interface;

and returning a second operation response to the client, wherein the second operation response carries the identifier of the window interface.

4. The method of claim 3, wherein the generating the identification of the operator interface comprises:

generating an identifier of the operation interface according to the opening time of the operation interface; or,

and randomly generating the identifier of the operation interface.

5. The method according to claim 2 or 4, wherein the identifier of the operation interface is carried in the operation response in the form of a hidden field.

6. The method according to any one of claims 1, 2, and 4, wherein after the updating the page corresponding to the identifier of the operation interface in the cache space according to the first page update information, the method further includes:

clearing the identifier of the operation interface according to a preset strategy; or,

and receiving an update processing ending request sent by an operation interface on the client, and clearing the identifier of the operation interface.

7. The method according to claim 6, wherein the clearing the identifier of the operation interface according to a preset policy comprises:

and clearing the identifier of the operation interface according to a timing clearing strategy or a maximum identifier number limiting strategy.

8. The method according to any one of claims 1, 2, 4 and 7, wherein the operation interface is a browser window or a tab.

9. The method of any one of claims 1, 2, 4, and 7, wherein the cache space is a session layer, an information recording program, or a distributed memory object cache system.

10. A page data updating processing method is characterized by comprising the following steps:

after updating a first page of an operation interface, sending a first operation request to a server through the operation interface, wherein the first operation request comprises first page update information on the operation interface and an identifier of the operation interface, so that the server updates original page information of a page corresponding to the identifier of the operation interface into the first page update information;

receiving a first operation response sent by the server, wherein the first operation response comprises an identifier of the operation interface;

and analyzing the identifier of the operation interface from the first operation response.

11. The method according to claim 10, wherein the updating the first page of the operation interface includes:

sending a second operation request to the server through the operation interface, wherein the second operation request needs to update the operation interface;

and receiving a second operation response sent by the server, wherein the second operation response carries the identifier of the window interface.

12. A server, comprising:

the client side comprises a receiving module and a processing module, wherein the receiving module is used for receiving a first operation request sent by an operation interface on a client side, the first operation request comprises first page update information on the operation interface and an identifier of the operation interface, and the first operation request is sent after the client side updates the first page of the operation interface;

and the processing module is used for updating the page corresponding to the identifier of the operation interface in the cache space according to the first page update information so as to update the original page information of the page corresponding to the identifier of the operation interface into the first page update information.

13. The server according to claim 12, wherein the server further comprises:

and the first sending module is used for sending a first operation response to the client, wherein the first operation response comprises the identifier of the operation interface.

14. The server according to claim 12 or 13, wherein the receiving module is further configured to:

receiving a second operation request sent by an operation interface on the client, wherein the second operation request indicates that the operation interface needs to be updated;

the processing module is further used for generating an identifier of the operation interface;

the server further comprises a second sending module, which is used for returning a second operation response to the client, wherein the second operation response carries the identifier of the window interface.

15. The server according to claim 14, wherein the processing module is specifically configured to:

generating an identifier of the operation interface according to the opening time of the operation interface; or,

and randomly generating the identifier of the operation interface.

16. The server according to claim 13 or 15, wherein the identifier of the operation interface is carried in the operation response in a hidden field.

17. The server according to any one of claims 12, 13, and 15, further comprising:

the clearing module is used for clearing the identifier of the operation interface according to a preset strategy; or when the receiving module receives an update processing ending request sent by an operation interface on the client, the identifier of the operation interface is cleared.

18. The server according to claim 17, wherein the purge module is specifically configured to:

and clearing the identifier of the operation interface according to a timing clearing strategy or a maximum identifier number limiting strategy.

19. The server according to any one of claims 12, 13, 15 and 18, wherein the operation interface is a browser window or a tab.

20. The server according to any one of claims 12, 13, 15, and 18, wherein the cache space is a session layer, an information recording program, or a distributed memory object cache system.

21. A client, comprising:

the sending module is used for sending a first operation request to a server through an operation interface after updating a first page of the operation interface, wherein the first operation request comprises first page update information on the operation interface and an identifier of the operation interface, so that the server updates original page information of a page corresponding to the identifier of the operation interface into the first page update information;

a receiving module, configured to receive a first operation response sent by the server, where the first operation response includes an identifier of the operation interface;

and the analysis module is used for analyzing the identifier of the operation interface from the first operation response.

22. The client of claim 21, wherein the sending module is configured to:

sending a second operation request to the server through an operation interface, wherein the second operation request needs to update the operation interface;

the receiving module is further configured to receive a second operation response sent by the server, where the second operation response carries an identifier of the window interface.