Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The list page updating method provided by the embodiment of the application can be applied to updating of a list page on a mobile device, for example, a list view type page in an ios or Andriod system, fig. 1 illustrates an example of a list page, and the bill information can be displayed to a user in a list page form at a payment client on a smart phone.
As shown in fig. 1, a plurality of entries may be included in the list page, for example, entry 11 displays: the user carries out the operation of transferring the balance treasures to the bank card in 14 days in 1 month, the transfer amount is 3000, and the current state is the transaction success; the operation time (day 14/1 month), the operation information (balance is transferred to the bank card), the operation amount (3000), the operation state (transaction success), and the like may be referred to as "entry information" to be displayed. For another example, the entry information in the entry 12 includes: the expenditure 150 is consumed in the yellow dragon kalaysia restaurant 305 at day 1 and day 13, and the state is that the transaction is successful. Other entries are not described in detail.
In addition, for example, 30 entries in total may be included in the "my bill", and only 8 entries are displayed in the page illustrated in fig. 1, and in this embodiment, the current display screen where the 8 entries are located may be referred to as a "current list page" and is a part of the "my bill" list page (30 entries in total). When the user operates one of the entries, the update of the list page is triggered, for example, the status in the entry 13 illustrated in fig. 1 is still "waiting for confirmation of receipt", the user may click on the entry 13 to perform the operation of confirming receipt of the entry, and the status of the entry 13 is changed to "transaction success" after the operation is completed. Such an update of the entry will trigger an update of the list page where the entry is located, and the list page update method of the present embodiment will be used to explain how to update the list page in the above case, and the update method may be executed by a client, such as the payment client illustrated in fig. 1.
Fig. 2 illustrates a flow of the list page updating method of the present embodiment, which may include:
201. when an operation request for a target record item is received, acquiring and storing page information of a current list page where the target record item is located;
202. and when a display request of returning the operation target record item to the list page is received, displaying the stored current list page according to the page information, wherein the current list page comprises the updated target record item.
Taking the state change of the entry 13 illustrated in fig. 1 as an example, the user will operate on the entry 13 to complete the confirmation of receipt. In step 201, the user clicks on an entry 13, and this entry 13 may be referred to as a "target entry", and the target entry is used to indicate an entry operated by the user. At this time, the payment client will receive an operation request for the target entry, which is triggered by the user clicking on the selection entry 13 and indicates that the user wants to request an operation on the entry.
The client will accordingly send a record operation request to the server (e.g., paymate server) requesting the server to feed back a record detail page corresponding to the target record, such as the "bill detail" page illustrated in fig. 3, which is transmitted by the server to the client and displayed by the client to the user. The user can click on 'confirm receipt', the client feeds back the confirmation receipt information to the server, and the server feeds back the latest status 'transaction success' to the client after changing the status of the record item, as shown in the example of fig. 3. For the above-mentioned interaction between the client and the server in the item status updating process, conventional techniques may be used, and details are not described, but only in this process, the client may receive the updated status information for the target item fed back by the server, such as the above-mentioned change of the status of the item 13 to "transaction success".
In this embodiment, when a user operates a record item, the client performs the following operations in addition to performing the update interaction of the record item information: when receiving an operation request for the target record item, the page information of the current list page where the target record item is located is also obtained and stored.
With reference to the example of fig. 1, when the user clicks the entry 13, the client acquires page information of a current list page where the entry 13 is located, where the current list page is the list page displayed on the smartphone shown in fig. 1, the list page includes eight entries, and the page information includes: which entries are included in the current page, for example, the ninth entry to the sixteenth entry (30 entries in total, which may be sorted according to the generation time in the list, and the page includes 9 th to 16 th entries), and entry information (for example, operation time, operation amount, operation status, etc.) of each entry, and with these pieces of information, the list page of fig. 1 can be displayed. The client stores the page information for subsequent redisplay of the list page according to the page information.
Referring to the example of fig. 4, for the above-mentioned page information of the current list page, which is also transmitted by the server to the client, the client receives the page information before the user performs the click entry operation of fig. 1, and displays the page information in a list manner (e.g., listview control) into the list interface form shown in fig. 1. In the above embodiment, for example, the module responsible for displaying the page information may record the entry identifier of each entry included in the current list page where the displayed entry 13 is located, for example, the identifier of the entry 11 is a1, and the identifier of the entry 13 is a2 (the identifier may be a unified entry identifier known by both the client and the server, and the server uniquely represents the entry by using the identifier when storing the entry information); moreover, the module responsible for displaying the page information may acquire which record item in the current list page is operated by the user, and notify the module receiving the page information to store the page information of the current list page, for example, store the record item information of each record item included in the page in the cache.
At 202, the client may also receive a display request for returning the operation target entry to the list page, for example, as illustrated in fig. 3, when the user operates the entry to confirm the receipt and completes the transaction, the status of the entry has changed to "transaction success", at which point the user may click on the "return" option at the top of the entry details page, and click on the return indicates that the user is to return to the original list page (i.e., the list page illustrated in fig. 1 where the entry details are entered). The client will hereby display the current list page of the example of fig. 1, such as the entry information comprising the ninth entry to the sixteenth entry, according to the page information of the list page stored in 201.
As in the example of fig. 5, in the entry information of entry 13 in the list page of the return display, the status has been changed from "waiting for confirmation of receipt" to "transaction success" in fig. 1, and the other entries are not changed. For the status update of the record item 13, two optional update modes of the target record item 13 are listed as follows, which may be performed as follows:
in an example, when storing the page information of the current list page where the target entry is located in 201, the client may further mark the target entry operated by the user in addition to storing the entry information of each entry in the current list page, where the mark refers to setting an "operated identifier," for example, the operated identifier may be "01" (for example, the operated identifier may be flexibly set in actual implementation), and the record with the operated identifier is set to indicate that the user operates the record.
As shown in fig. 6, the client stores page information of the current list page shown in fig. 1, in which the entry information of the entry 13, the status information is "waiting for confirmation of receipt", and the entry 13 has been marked with the operation identifier. After the user confirms the delivery operation illustrated in fig. 3, the client also receives the latest status information "transaction success" of the record item 13 transmitted by the server, and the status page is already displayed to the user (see fig. 3).
In this embodiment, the client may compare the entry information of the operated entry sent by the server with a target entry corresponding to the operated identifier in the stored current list page, and determine whether the target entry is updated. Specifically, for example, the client may check that, in the stored page information, the record item 13 with the record item identifier "a 2" is marked with the operated identifier "01", the record item identifier of the record item information transmitted by the server is also "a 2", the two record item information correspond to the same record item, the client compares the two items of information, and finds that the status information in the record item information is different, one is "waiting for confirmation of receipt", the other is "transaction success", and of course, other different information, such as the operation time, may exist. The client can determine that the target record item is updated, update the record item information of the target record item into the record item information sent by the server, and display the target record item according to the updated information when the list page is displayed. As illustrated in fig. 5, in this list page, only the information of entry 13 is updated and none of the other entries is changed, as compared with the list page of fig. 1.
In another example, the client may also send an information acquisition request to the server when receiving a display request to return to the list page, such as detecting that the user clicked "return", and request to acquire information of a target entry, such as entry 13, such as the operating status in that entry 13. The client can know which record item is operated in the list page according to the recorded operated identifier, the record item with the operated identifier is set to represent that the user operates the record item, the client only requests the record item information marked with the operated identifier from the server, and other record items do not need to request the server because the user does not operate and the information is not updated. Based on the above, the client may carry the record item identifier of the target record item corresponding to the operated identifier in the information acquisition request, so that the server knows which record item information the client requests, returns the record item information corresponding to the record item identifier to the client, and the client displays the target record item information in the list page. In this way, since the client acquires only the target entry information operated by the user from the server, not all the information of the list page, the efficiency of information acquisition and page update can also be improved.
The list page update method of the present embodiment is compared with the list page update in the conventional manner as follows:
on one hand, in the conventional manner, when the client receives a display request for returning to the list page (for example, when the user clicks "return" in fig. 3), the client will request the list page from the server again, the server also transmits page information of the entire list page including 30 entries to the client, and the client displays the list page, that is, the page information is transmitted again each time the list page is updated; in this embodiment, the client has previously stored the page information of the list page where the target entry is located, and when a return display request is received, the client does not need to request the server, but only needs to display the previous list page according to the stored page information, even if some entries are updated, the server only transmits the information of the target entry to the client, and does not need to transmit all the information of the entries to the client, thereby reducing interactive transmission between the client and the server, reducing waste of network resources, and also improving the display efficiency of the list page. Alternatively, when receiving the return display request, the client may obtain only the operated target entry information from the server instead of obtaining all the list page information, thereby reducing the waste of network resources and increasing the page display efficiency.
On the other hand, this way can make the user still see the target record item operated before himself when returning to the list page, for example, the user clicks the operation record item 13 in fig. 1, and when the operation is finished returning to the list page, as shown in fig. 5, the user still can see the record item 13 and see the changed information (e.g., the transaction is successful) of the record item 13; however, in the conventional manner, as described above, the client reloads the entire list page, for example, the entries 13 operated by the user are located on the second screen (the user can see only by sliding the screen to the second screen, and each screen assumes that only eight entries can be seen) in the entire list page (30 entries in total), and when the client reloads the entire list page, the user firstly sees the first to eighth entries (i.e., displays from the beginning) after returning to the list page, and the user needs to manually turn pages to see the operated entries 13, which is very inconvenient. Therefore, the mode of the embodiment can enable the user to see the updating state of the record items in time, and the user can conveniently check the updating.
In addition, it is assumed that after the user operates the target entry, the information of the entry is not updated, for example, in fig. 6, the client compares the entry information sent by the server with the entry information corresponding to the operated identifier in the stored page information, and if the two are the same, it indicates that the record information may not change after the operation, and the client may still display the list page according to the stored page information.
In order to implement the above list page updating method, the present embodiment further provides a list page updating apparatus, which is provided at the client. As shown in fig. 7, the apparatus may include: an information recording module 71 and a page updating module 72; wherein,
the information recording module 71 is configured to, when receiving an operation request for a target entry, acquire and store page information of a current list page where the target entry is located;
and a page updating module 72, configured to, when a display request for returning an operation target entry to a list page is received, display the stored current list page according to the page information, where the current list page includes the updated target entry.
Further, the page information of the current list page includes: and the current list page comprises record item information of each record item.
Further, the information recording module 71 is specifically configured to obtain record item identifiers of record items of the current list page where the target record item is located, and store record item information corresponding to the identifiers according to the record item identifiers.
As shown in fig. 8, the apparatus may further include: a record marking module 73, configured to set an operated identifier for a target record item included in the current list page when an operation request for the target record item is received.
In addition, page update module 72 may include: a comparison unit 721 and an update unit 722; wherein,
a comparing unit 721, configured to compare the entry information of the target entry sent by the server with the target entry corresponding to the operated identifier in the stored current list page, and determine whether the target entry is updated;
and the updating unit 722 is configured to update the target record item corresponding to the operated identifier in the current list page to the record item information of the target record item sent by the server when the information of the target record item is updated.
As shown in fig. 9, in another example, the page update module 72 of the apparatus may further include: an information request unit 723 and an information display unit 724; wherein,
an information request unit 723, configured to send an information acquisition request for requesting to acquire target record item information to a server, where the information acquisition request includes a record item identifier of a target record item corresponding to the operated identifier;
an information display unit 724, configured to receive target entry information returned by the server according to the entry identifier, and display the target entry information in the current list page.
The specific working principle of each module of the above device can be referred to in combination with the method embodiment, and is not described in detail. By setting the list page updating device at the client, the waste of network resources is reduced when the list page is updated, the cost is saved, and the user can conveniently check the updated content.
The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.