CN104182252A - App version incremental updating method - Google Patents
App version incremental updating method Download PDFInfo
- Publication number
- CN104182252A CN104182252A CN201410396636.2A CN201410396636A CN104182252A CN 104182252 A CN104182252 A CN 104182252A CN 201410396636 A CN201410396636 A CN 201410396636A CN 104182252 A CN104182252 A CN 104182252A
- Authority
- CN
- China
- Prior art keywords
- good friend
- version number
- client
- increment
- list
- 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
Links
Abstract
The invention provides an APP (Application) version incremental updating method, mainly designed for communication softwares in a handheld device to realize friend incremental updating. The method comprises the following steps: added, deleted and modified friend information version numbers are recorded through a service terminal and then stored in a buffer data base; the increment is obtained and the friend information incremental updating is completed after data in the buffer data base is read and the incremental updating request is sent by a client. The App version incremental updating method has the advantages as follows: when a user needs to modify friend information, all needed is to access to the friend list and then acquire the incremental updating of the friend information without getting the information lists of all friends, so that the data flow usage of a client is reduced, the problem that the request speed of an interface is slow is solved, and the program running of the APP is smoother.
Description
Technical field
The present invention relates to a kind of increment updating method, more particularly, relate to a kind of increment updating method about application version.
Background technology
At present, when application data in handheld device upgrades, client all will be obtained data to complete renewal to server request full dose at every turn, so not only interface requests speed is slow and client to expend flow many, to service end, also can cause very large pressure simultaneously.
Redis be a use ANSI C language compilation of increasing income, network enabled, can also can persistence based on internal memory log type, Key-Value database, and provide multilingual application programming interface (API).Redis has been used two kinds of file layouts: full dose data and incremental re-quest.Full dose data layout is that the data in internal memory are write to disk, is convenient to next file reading and loads; Incremental re-quest file is that the data sequence in internal memory is turned to operation requests, carries out replay obtain data for file reading.When application data upgrades, client sends incremental re-quest, can be from Redis buffer memory reading out data.
Summary of the invention
The technical problem to be solved in the present invention, be to provide a kind of APP(application program) version increment updating method, mainly for the bitcom in handheld device, realize good friend's incremental update, the good friend's data version number that records increase, deletes and revise by service end, and deposit cache database in, client sends after incremental update request reading out data from buffer memory, obtains increment, completes good friend's data incremental update.Accelerate like this interface requests speed and reduced the use of flow.
The technical problem to be solved in the present invention is achieved in that a kind of APP version increment updating method, comprises the increment updating method of same equipment and the increment updating method between distinct device:
The increment updating method of described same equipment comprises:
Step 10, handheld device, it is the existing version number that corresponding member's sequence number of each good friend in the bitcom APP in client and initial value are 1, described member's sequence number and existing version number form a buddy list: if a good friend's personal information wherein, while comprising six attribute modification of user's name, head portrait, last entry address, last activity time, state and vital values, existing version number corresponding to this good friend increases by 1;
Step 11, existing good friend of database initialize of server end, upgrade list, in table, record six attributes of personal information described in good friend's latest edition this shop and step 10 and distinguish corresponding attribute version number, the initial value of described latest edition this shop and attribute version number is 1, when in six attributes of good friend's personal information, one or plurality of attributes are updated, good friend's latest edition this shop increases by 1, and the corresponding attribute version number modification of the attribute being updated is that described latest edition this shop increases the value after 1, and the attribute version number that other are not updated is constant;
The first full dose of step 12, user is obtained the buddy list not upgrading, and is then kept at client, and during each incremental update buddy list, client is by the described buddy list the not upgrading end of uploading onto the server;
Step 13, server end obtain the buddy list after renewal from buffer memory, the buddy list not upgrading described in contrast step 12: if member's sequence number that server end exists and client does not exist, illustrate that good friend corresponding to this member's sequence number is new interpolation, all adds in increment list by the corresponding good friend's of this member's sequence number existing version number with the Liu Ge attribute version number of personal information; If the non-existent member's sequence number of server end and client exist, illustrate that good friend corresponding to this member's sequence number is deleted, the corresponding good friend's of this member's sequence number existing version number is added in increment list with member's sequence number, and this good friend's existing version number is designated as to-1, represent that member's sequence number corresponding to this good friend delete from buddy list;
Step 14, integrating step 13; according to corresponding member's sequence number and the existing version number of residue good friend; from existing good friend described in step 11, upgrade list and to take out the record that latest edition this shop in residue good friend is greater than existing version number; then the Liu Ge attribute version number of this good friend's personal information is contrasted with attribute version number corresponding in the buddy list not upgrading described in step 12 respectively; if wherein there is the attribute version number of attribute to be greater than attribute version number corresponding in the buddy list not upgrading, the attribute version number that takes out this attribute adds in increment list;
Step 15, server end all deposit the buddy list after upgrading in Redis cache database at every turn; when client-requested incremental update; client is first obtained increment and from Redis cache database, is read the data that described increment is corresponding again from increment list, realizes client incremental update buddy list;
Increment updating method between described distinct device comprises:
Step 20, the client release number logging in are for the first time designated as 1, and every use afterwards once different client logs in, and client release number can increase by 1 successively, and the highest client release number is returned to server end version number;
Step 21, by client release number and the contrast of server end version number, if client release number is less than server end version number, client-requested incremental update, client is first obtained increment and from Redis cache database, is read the data that described increment is corresponding again from increment list, realizes client incremental update buddy list.
Further, described server end is to revising good friend's remarks, increase, delete and revise the operation of good friend's grouping, server end will first judge in the buddy list after described renewal, whether have corresponding member's sequence number and existing version number: if having, existing version number corresponding to good friend of deleting can be designated as-1 in increment list, existing version number corresponding to good friend of revising increases by 1 postscript in increment list, existing version number corresponding to good friend increasing can add in increment list, and the buddy list after at every turn upgrading is deposited in Redis cache database, convenient service device end and client are extracted data.
Tool of the present invention has the following advantages: the method that goes up good friend's incremental update by APP realizes when user good friend revises data, user enters buddy list only need to obtain the incremental update of good friend's data, and need not obtain all good friends' information list, the flow that has reduced client is used, also solved the slow-footed problem of interface requests, made APP operation more smooth.
Accompanying drawing explanation
The present invention is further illustrated in conjunction with the embodiments with reference to the accompanying drawings.
Fig. 1 is that the present invention is at the method flow diagram of same equipment incremental update.
Fig. 2 is the method flow diagram of the present invention's incremental update between distinct device.
Embodiment
Shown in Fig. 1, as follows in the increment updating method detailed process of same equipment:
Step 10, handheld device, be the existing version version that corresponding member's sequence number memberID of each good friend in the bitcom in client and initial value are 1, described memberID and version form a buddy list: if a good friend's personal information wherein, while comprising six attribute modification of user's name, head portrait, last entry address, last activity time, state and vital values, version corresponding to this good friend increases by 1;
Step 11, existing good friend of database initialize at server end upgrades list t_member_update_log, in table, record six attributes of personal information described in good friend's the newest-version of latest edition this shop and step 10 and distinguish corresponding attribute version number, the initial value of described newest-version and attribute version number is 1, when in six attributes of good friend's personal information, one or plurality of attributes are updated, good friend's newest-version increases by 1, and the corresponding attribute version number modification of the attribute being updated is that described newest-version increases the value after 1, the attribute version number that other are not updated is constant,
The first full dose of step 12, user is obtained the buddy list not upgrading, and is then kept at client, and during each incremental update buddy list, client is by the described buddy list the not upgrading end of uploading onto the server;
Step 13, server end obtain the buddy list after renewal from buffer memory, the buddy list not upgrading described in contrast step 12: if the memberID that server end exists and client does not exist, illustrate that the good friend that this memberID is corresponding is new interpolation, corresponding good friend's the version of this memberID and the Liu Ge attribute version number of personal information are added in increment list; If the non-existent memberID of server end and client exist, illustrate that the good friend that this memberID is corresponding is deleted, the corresponding good friend's of this memberID version and memberID are added in increment list, and this good friend's version is designated as to-1, represent that memberID corresponding to this good friend deletes from buddy list;
Step 14, integrating step 13; according to corresponding memberID and the version of residue good friend; from t_member_update_log described in step 11, take out the record that newest-version in residue good friend is greater than version; then the Liu Ge attribute version number of this good friend's personal information is contrasted with attribute version number corresponding in the buddy list not upgrading described in step 12 respectively; if wherein there is the attribute version number of attribute to be greater than attribute version number corresponding in the buddy list not upgrading, the attribute version number that takes out this attribute adds in increment list;
Step 15, server end all deposit the buddy list after upgrading in Redis cache database at every turn, when client-requested incremental update, client is first obtained increment and from Redis cache database, is read the data that described increment is corresponding again from increment list, realizes client incremental update buddy list.
Increment updating method between described distinct device comprises:
Step 20, the client release number logging in are for the first time designated as 1, and every use afterwards once different client logs in, and client release number can increase by 1 successively, and the highest client release number is returned to server end version number;
Step 21, by client release number and the contrast of server end version number, if client release number is less than server end version number, client-requested incremental update, client is first obtained increment and from Redis cache database, is read the data that described increment is corresponding again from increment list, realizes client incremental update buddy list.
Although more than described the specific embodiment of the present invention; but being familiar with those skilled in the art is to be understood that; our described specific embodiment is illustrative; rather than for the restriction to scope of the present invention; those of ordinary skill in the art are in equivalent modification and the variation done according to spirit of the present invention, all should be encompassed in the scope that claim of the present invention protects.
Claims (2)
1. an APP version increment updating method, is characterized in that, comprises the increment updating method of same equipment and the increment updating method between distinct device: the increment updating method of described same equipment comprises:
Step 10, handheld device, be the corresponding member's sequence number of each good friend and the existing version number in the bitcom in client, described existing version number is provided with initial value, described member's sequence number and existing version number form a buddy list: if a good friend's personal information wherein, comprise in six attributes of user's name, head portrait, last entry address, last activity time, state and vital values that when one or plurality of attributes are upgraded, existing version numerical value corresponding to this good friend can increase;
Step 11, existing good friend of database initialize at server end upgrades list, in table, record six attributes of personal information described in good friend's latest edition this shop and step 10 and distinguish corresponding attribute version number, described latest edition this shop and attribute version number are equipped with initial value, when in six attributes of good friend's personal information, one or plurality of attributes are updated, good friend's latest edition this shop numerical value increases, and the corresponding attribute version number modification of the attribute being updated is the value after described latest edition this shop numerical value increases, the attribute version number that other are not updated is constant,
The first full dose of step 12, user is obtained the buddy list not upgrading, and is then kept at client, and during each incremental update buddy list, client is by the described buddy list the not upgrading end of uploading onto the server;
Step 13, server end obtain the buddy list after renewal from buffer memory, the buddy list not upgrading described in contrast step 12: if member's sequence number that server end exists and client does not exist, illustrate that good friend corresponding to this member's sequence number is new interpolation, all adds in increment list by the corresponding good friend's of this member's sequence number existing version number with the Liu Ge attribute version number of personal information; If the non-existent member's sequence number of server end and client exist, illustrate that good friend corresponding to this member's sequence number is deleted, the corresponding good friend's of this member's sequence number existing version number is added in increment list with member's sequence number, and this good friend's existing version number is designated as to negative, represent that member's sequence number corresponding to this good friend delete from buddy list;
Step 14, integrating step 13; according to corresponding member's sequence number and the existing version number of residue good friend; from existing good friend described in step 11, upgrade list and to take out the record that latest edition this shop in residue good friend is greater than existing version number; then the Liu Ge attribute version number of this good friend's personal information is contrasted with attribute version number corresponding in the buddy list not upgrading described in step 12 respectively; if wherein there is the attribute version number of attribute to be greater than attribute version number corresponding in the buddy list not upgrading, the attribute version number that takes out this attribute adds in increment list;
Step 15, server end all deposit the buddy list after upgrading in Redis cache database at every turn; when client-requested incremental update; client is first obtained increment and from Redis cache database, is read the data that described increment is corresponding again from increment list, realizes client incremental update buddy list;
Increment updating method between described distinct device comprises:
Step 20, the client release number logging in are for the first time provided with initial value, and every use afterwards once different client logs in, and client release numerical value can increase successively, and the highest client release number is returned to server end version number;
Step 21, by client release number and the contrast of server end version number, if client release number is less than server end version number, client-requested incremental update, client is first obtained increment and from Redis cache database, is read the data that described increment is corresponding again from increment list, realizes client incremental update buddy list.
2. a kind of APP version increment updating method according to claim 1, it is characterized in that, described server end is to revising good friend's remarks, increase, delete and revise the operation of good friend's grouping, server end will first judge in the buddy list after described renewal, whether have corresponding member's sequence number and existing version number: if having, existing version number corresponding to good friend of deleting can be designated as negative in increment list, existing version numerical value corresponding to good friend of revising increases postscript in increment list, existing version number corresponding to good friend increasing can add in increment list, and the buddy list after at every turn upgrading is deposited in Redis cache database.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410396636.2A CN104182252A (en) | 2014-08-13 | 2014-08-13 | App version incremental updating method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201410396636.2A CN104182252A (en) | 2014-08-13 | 2014-08-13 | App version incremental updating method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104182252A true CN104182252A (en) | 2014-12-03 |
Family
ID=51963328
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201410396636.2A Pending CN104182252A (en) | 2014-08-13 | 2014-08-13 | App version incremental updating method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104182252A (en) |
Cited By (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105704254A (en) * | 2016-04-27 | 2016-06-22 | 努比亚技术有限公司 | Advertisement filtering method, client side and server side |
| CN105763369A (en) * | 2016-02-04 | 2016-07-13 | 湖南长城信息金融设备有限责任公司 | Terminal equipment remote software version distribution method and system |
| CN106886548A (en) * | 2016-08-03 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Data query method and device |
| CN106970974A (en) * | 2017-03-27 | 2017-07-21 | 车智互联（北京）科技有限公司 | A kind of APP low discharges data update system and method based on version |
| CN107733781A (en) * | 2017-09-19 | 2018-02-23 | 上海掌门科技有限公司 | A kind of processing method of instant messaging, equipment and computer-readable storage medium |
| CN108228271A (en) * | 2016-12-22 | 2018-06-29 | 凡学（上海）教育科技有限公司 | A kind of attribute configuration method, equipment and application for CAI software user |
| CN108259562A (en) * | 2017-12-11 | 2018-07-06 | 杭州品茗安控信息技术股份有限公司 | A kind of method of data synchronization and device based on multi-endpoint |
| CN108304408A (en) * | 2017-01-12 | 2018-07-20 | 中国移动通信集团公司 | A kind of data cached method for refreshing and device |
| CN109284300A (en) * | 2018-08-31 | 2019-01-29 | 江苏龙虎网信息科技股份有限公司 | A kind of client mass data real time updating method |
| CN109558465A (en) * | 2018-11-22 | 2019-04-02 | 北京酷我科技有限公司 | Relationship management method and system in a kind of social intercourse system between user |
| CN110502169A (en) * | 2018-05-18 | 2019-11-26 | 华为技术有限公司 | A kind of display control method and terminal |
| CN110727895A (en) * | 2019-10-09 | 2020-01-24 | 北京达佳互联信息技术有限公司 | Sensitive word sending method and device, electronic equipment and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252617A (en) * | 2008-03-25 | 2008-08-27 | 宇龙计算机通信科技(深圳)有限公司 | Synchronizing method and synchronizing system of linkmen between host computer and secondary computer |
| CN101582859A (en) * | 2009-04-23 | 2009-11-18 | 腾讯科技（北京）有限公司 | Instant messaging tool adding friends processing method, instant messaging device and system |
| US8001095B2 (en) * | 2004-02-12 | 2011-08-16 | Pioneer Corporation | Method of updating a version of an application program |
-
2014
- 2014-08-13 CN CN201410396636.2A patent/CN104182252A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8001095B2 (en) * | 2004-02-12 | 2011-08-16 | Pioneer Corporation | Method of updating a version of an application program |
| CN101252617A (en) * | 2008-03-25 | 2008-08-27 | 宇龙计算机通信科技(深圳)有限公司 | Synchronizing method and synchronizing system of linkmen between host computer and secondary computer |
| CN101582859A (en) * | 2009-04-23 | 2009-11-18 | 腾讯科技（北京）有限公司 | Instant messaging tool adding friends processing method, instant messaging device and system |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105763369A (en) * | 2016-02-04 | 2016-07-13 | 湖南长城信息金融设备有限责任公司 | Terminal equipment remote software version distribution method and system |
| CN105763369B (en) * | 2016-02-04 | 2018-08-17 | 湖南长城信息金融设备有限责任公司 | A kind of terminal unit remote software version distribution method and system |
| CN105704254A (en) * | 2016-04-27 | 2016-06-22 | 努比亚技术有限公司 | Advertisement filtering method, client side and server side |
| CN106886548B (en) * | 2016-08-03 | 2020-06-30 | 阿里巴巴集团控股有限公司 | Data query method and device |
| CN106886548A (en) * | 2016-08-03 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Data query method and device |
| CN108228271A (en) * | 2016-12-22 | 2018-06-29 | 凡学（上海）教育科技有限公司 | A kind of attribute configuration method, equipment and application for CAI software user |
| CN108228271B (en) * | 2016-12-22 | 2021-12-14 | 凡学（上海）教育科技有限公司 | Attribute configuration method, equipment and application for educational software users |
| CN108304408A (en) * | 2017-01-12 | 2018-07-20 | 中国移动通信集团公司 | A kind of data cached method for refreshing and device |
| CN108304408B (en) * | 2017-01-12 | 2021-04-02 | 中国移动通信集团公司 | Cache data refreshing method and device |
| CN106970974A (en) * | 2017-03-27 | 2017-07-21 | 车智互联（北京）科技有限公司 | A kind of APP low discharges data update system and method based on version |
| CN107733781A (en) * | 2017-09-19 | 2018-02-23 | 上海掌门科技有限公司 | A kind of processing method of instant messaging, equipment and computer-readable storage medium |
| CN107733781B (en) * | 2017-09-19 | 2021-06-22 | 上海掌门科技有限公司 | Instant messaging processing method, equipment and computer storage medium |
| CN108259562A (en) * | 2017-12-11 | 2018-07-06 | 杭州品茗安控信息技术股份有限公司 | A kind of method of data synchronization and device based on multi-endpoint |
| CN108259562B (en) * | 2017-12-11 | 2022-02-25 | 杭州品茗安控信息技术股份有限公司 | Data synchronization method and device based on multiple endpoints |
| CN110502169A (en) * | 2018-05-18 | 2019-11-26 | 华为技术有限公司 | A kind of display control method and terminal |
| CN109284300A (en) * | 2018-08-31 | 2019-01-29 | 江苏龙虎网信息科技股份有限公司 | A kind of client mass data real time updating method |
| CN109558465A (en) * | 2018-11-22 | 2019-04-02 | 北京酷我科技有限公司 | Relationship management method and system in a kind of social intercourse system between user |
| CN110727895A (en) * | 2019-10-09 | 2020-01-24 | 北京达佳互联信息技术有限公司 | Sensitive word sending method and device, electronic equipment and storage medium |
| CN110727895B (en) * | 2019-10-09 | 2022-07-22 | 北京达佳互联信息技术有限公司 | Sensitive word sending method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104182252A (en) | App version incremental updating method | |
| CN108021336B (en) | Data layout method, system and storage medium for seamless data migration | |
| CN102741843B (en) | Method and apparatus for reading data from database | |
| US9223564B2 (en) | Update systems responsive to ongoing processing at a storage system | |
| US9965207B2 (en) | Maintenance of cloned computer data | |
| CN107911249B (en) | Method, device and equipment for sending command line of network equipment | |
| US9679021B2 (en) | Parallel transactional-statistics collection for improving operation of a DBMS optimizer module | |
| US20160188227A1 (en) | Method and apparatus for writing data into solid state disk | |
| CN103559301A (en) | Method of data update, database trigger and SE (search engine) | |
| JP2013509658A (en) | Allocation of storage memory based on future usage estimates | |
| CN103902562A (en) | Method and device for upgrading terminal databases | |
| CN108932286A (en) | A kind of date storage method, data query method and device | |
| CN104423982A (en) | Request processing method and device | |
| CN105446794A (en) | Disc operation method, apparatus and system based on virtual machine | |
| US9104567B2 (en) | Memory-leak identification | |
| CN104052626A (en) | Method, device and system for configuring network element data | |
| CN103713926A (en) | Method and system for updating software of client in advance | |
| US11080909B2 (en) | Image layer processing method and computing device | |
| CN107169126A (en) | A kind of log processing method and relevant device | |
| CN107436761B (en) | UEFI (unified extensible firmware interface) system and traditional system coexistence management method based on UEFI mainboard | |
| CN103501341A (en) | Method and device for establishing Web service | |
| CN101510156A (en) | Information system resource recovery method and device | |
| US11176089B2 (en) | Systems and methods for implementing dynamic file systems | |
| CN101458628A (en) | Program edition management method | |
| CN106775456B (en) | A kind of data processing method, apparatus and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| WD01 | Invention patent application deemed withdrawn after publication | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20141203 |