CN103595808B - A kind of file update information method for pushing and device - Google Patents
A kind of file update information method for pushing and device Download PDFInfo
- Publication number
- CN103595808B CN103595808B CN201310589829.5A CN201310589829A CN103595808B CN 103595808 B CN103595808 B CN 103595808B CN 201310589829 A CN201310589829 A CN 201310589829A CN 103595808 B CN103595808 B CN 103595808B
- Authority
- CN
- China
- Prior art keywords
- file destination
- file
- client
- renewal
- updated
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Abstract
The embodiment of the invention discloses a kind of file update information method for pushing and device, the described method includes：Receive the message that file destination is updated；In having the client of requirements for access to the file destination, the push object of fresh information is determined；To the fresh information of file destination described in identified push Object Push.Using the embodiment of the present invention, the client that can to have access target file demand knows the fresh information of file in time.
Description
Technical field
The present invention relates to network communication technology field, more particularly to a kind of file update information method for pushing and device.
Background technology
With the development of network technology, multiple client can access the same file of server end at the same time, such as：Text
This document, picture file, video file, audio file etc..In the prior art, when a certain client pair in multiple client
After this document has carried out renewal operation, other clients manually can only detect or close the side that this document reopens again
Formula, learns that this document has been updated, and therefore, other clients can not know the fresh information of this document in time.
The content of the invention
The embodiment of the invention discloses a kind of file update information method for pushing and device, so that received server-side arrives
After the message that file destination is updated, the renewal of this document can be known in time by being determined the client of reception file update information
Information.
To reach above-mentioned purpose, the embodiment of the invention discloses a kind of file update information method for pushing, the method bag
Include：
Receive the message that file destination is updated；
In having the client of requirements for access to the file destination, the push object of fresh information is determined；
To the fresh information of file destination described in identified push Object Push.
Preferably, it is described in having the client of requirements for access to the file destination, determine the push pair of fresh information
As being：
Determine before the message that file destination is updated is received, accessing the client of the file destination.
Preferably, described determine before the message that file destination is updated is received, the visitor of the file destination is being accessed
Family end, including：
Determine all clients for accessing file destination；
The client of file destination was accessed all, was determined before the message that file destination is updated is received, just
In the client of access target file.
Preferably, the fresh information, including：
The mark of file destination, the client identification for updating file destination, renewal time and/or renewal synopsis letter
Breath.
Preferably, after the push object of fresh information is determined, the file update information method for pushing further includes：
The file destination after renewal is sent to identified push object.
To reach above-mentioned purpose, the embodiment of the invention discloses a kind of file update information pusher, described device bag
Include：
File is updated message reception module, the message being updated for receiving file destination；
Client determining module, in having the client of requirements for access to the file destination, determining fresh information
Push object；
File update information pushing module, believes for the renewal to file destination described in identified push Object Push
Breath.
Preferably, the client determining module, specifically for determining before the message that file destination is updated is received, just
Accessing the client of the file destination.
Preferably, the client determining module, including：First determination sub-module and the second determination sub-module；
First determination sub-module, for determining all clients for accessing file destination；
Second determination sub-module, in the definitive result of first determination sub-module, determining receiving
Before the message that file destination is updated, the client just in access target file.
Preferably, the file update information pushing module, specifically for including target to identified client push
The mark of file, the client identification for updating file destination, renewal time and/or the fresh information for updating synopsis information.
Preferably, the file update information pusher further includes：Data transmission blocks after renewal；
Data transmission blocks after the renewal, for determining the push object of fresh information in the client determining module
Afterwards, the file destination after renewal is sent to identified push object.
As seen from the above technical solutions, in the present solution, after the message that received server-side is updated to file destination, to
It is determined receiving the client push file update information of file update information.With in the prior art, manually detecting or closing
Close this document and reopen file again, compared in a manner of detecting file and whether being updated, this programme enables to be determined connecing
The fresh information of this document can be known in time by receiving the client of file update information.
Brief description of the drawings
In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, below will be to embodiment or existing
There is attached drawing needed in technology description to be briefly described, it should be apparent that, drawings in the following description are only this
Some embodiments of invention, for those of ordinary skill in the art, without creative efforts, can be with
Other attached drawings are obtained according to these attached drawings.
Fig. 1 is a kind of file update information method for pushing flow diagram provided in an embodiment of the present invention；
Fig. 2 is another file update information method for pushing flow diagram provided in an embodiment of the present invention；
Fig. 3 is a kind of file update information pusher structure diagram provided in an embodiment of the present invention；
Fig. 4 is another file update information pusher structure diagram provided in an embodiment of the present invention.
Embodiment
Below in conjunction with the attached drawing in the embodiment of the present invention, the technical solution in the embodiment of the present invention is carried out clear, complete
Site preparation describes, it is clear that described embodiment is only part of the embodiment of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, those of ordinary skill in the art are obtained every other without creative efforts
Embodiment, belongs to the scope of protection of the invention.
Due in practical application, when multiple client accesses the identical file of server end at the same time, if wherein a certain visitor
After family end has carried out this document renewal operation, other clients can not know the fresh information of this document, therefore, this Shen in time
It please provide a kind of file update information method for pushing and device.
Below by specific embodiment, the present invention is described in detail.
Fig. 1 is a kind of file update information method for pushing flow diagram provided in an embodiment of the present invention, and this method can be with
Applied to server end, comprise the following steps：
Step 101：Receive the message that file destination is updated.
In practical application, multiple client can access a certain file destination of server end at the same time, which can
Think text document, image file, video file, audio file etc..One or more of multiple client client can
To be updated to the file destination, after file destination is updated, the message which is updated is sent to by client
Server end, after the message that received server-side to file destination is updated, triggers the operation of step 102.
After client is updated file destination, first the file destination after renewal can be sent to server end,
After file destination after to be updated is sent, then to server end send the message that is updated of file destination.Should but actual
In, since client is when sending the file destination after renewal to server end, easily by factors such as network bandwidth, file sizes
Influence, transmission file may need the long period, so, client can also first to server end send file destination by more
New message, retransmits the file destination after renewal, in order to which server end can push the letter that file destination is updated in time
Cease to client.But there may be client in this case to have been received by the message that file destination is updated, and update
File destination afterwards is not sent also to the situation of server completely.
In practical application, when multiple client or a client are repeatedly updated file destination, server
End can be according to the time sequencing for receiving file destination and being updated message, by the target text after the newest renewal of receiving time
Part, is determined as the file destination of latest edition, so that other clients access.
Such as：Customer end A has carried out renewal operation in 9 points of 10 minutes file X to server end；Customer end B is right 9: 30
The file X of server end has carried out renewal operation；Client C has carried out renewal operation in 9 points of 31 minutes X to server end, and
A, B, C have sent the message that file destination is updated to server end having updated the rear of file, then server end is received successively
To the message of A, B, C more new file X, and the X-File that the file after client C renewals is latest edition.
The application simply by taking time sequencing as an example, illustrates the feelings during message that the multiple files of received server-side are updated
Condition, is not limited only to this in practical application, for example, it is also possible to consider priority orders of client etc..
File destination is updated it should be noted that working as client, and the file destination after renewal is sent to server
Afterwards, server end can only retain the file destination of latest edition, can also retain the file destination after renewal every time, but only
It is supplied to client to access the file destination of latest edition.
Step 102：In having the client of requirements for access to the file destination, the push object of fresh information is determined.
In this step, there is the client of requirements for access, can include following several：
Before the message that received server-side file destination is updated, the client just in access target file；
Before the message that received server-side file destination is updated, all clients for accessing file destination；
All subscription file destinations update dynamic client；
All clients in same working group；
Etc..
In practical application, when identified push object is " before the message that file destination is updated is received, to access
During the client of the file destination ", all clients for accessing the file destination can be determined first, then in these clients
In end, determine before the message that file destination is updated is received, accessing the client of the file destination.
In addition, in a specific embodiment, server end can set one to be used to record each client access
The access list of server-side conditions, when a certain client accesses any one file in server, in the access list
Record current state information of the mark of the client, the file identification accessed, access time, client etc..Determining
Before receiving the message that file destination is updated, when accessing the client of the file destination, can according in access list,
The file identification of access and the correspondence of client identification determine all clients for accessing the file destination, further according to
The current state information of client, determines before receiving the message that file destination is updated, is accessing the file destination
Client.Certainly, the application is simply illustrated as example, determines that the mode of client is not limited only to this in practical application.
Step 103：To the fresh information of file destination described in identified push Object Push.
In this step, to the fresh information of the push Object Push file destination determined described in step 102, in the letter
The mark of at least one file destination is carried in breath, to inform that the push subject object file has been updated.
For example, identified push object is " before the message that file destination is updated is received, in a step 102
Access the client of the file destination ", then the renewal to these identified client push file destinations is believed in this step
Breath, through determining, if an only client is accessing renewal preceding document data, only to the client push fresh information；
If there is multiple client accessing the file data before renewal, fresh information is pushed to multiple client.
Fresh information can include：The mark of file destination, the client identification for updating file destination, renewal time and/
Or renewal synopsis information etc., in certain practical application, the content of fresh information is not limited only to this, such as can also wrap
Include：Update the version number etc. of file after the version number of preceding document, renewal.
Wherein, the mark of file destination, can be title, identification code, ID number of file destination etc.；Update file destination
Client identification, can be the title of client, IP address etc..The mark of file destination and more fresh target in practical application
The client identification of file is not limited only to this, as long as it can uniquely determine file destination and more fresh target text in a certain range
The mark of the client of part.
In practical application, after client receives the file update information of push, it can select to download the target after updating
File simultaneously shows the file destination after renewal, can also select not download the file destination after renewal, and continues to access
File destination before renewal ignores this document fresh information.
As seen from the above, in this programme after the message that received server-side to file destination is updated, by there is visit
Ask the mode of the client push fresh information of file destination demand so that each client can timely know this document quilt
The message of renewal.
Fig. 2 is another file update information method for pushing flow diagram provided in an embodiment of the present invention, and this method can
Applied to server end, to comprise the following steps：
Step 201：Receive the message that file destination is updated.
Step 202：In having the client of requirements for access to the file destination, the push object of fresh information is determined.
Step 203：The file destination after renewal is sent to identified push object.
Step 204：To the fresh information of file destination described in identified push Object Push.
It should be noted that step 201,202 and 204 in the present embodiment, can respectively with step in embodiment illustrated in fig. 1
101st, 102 is identical with 103, therefore, is not repeated herein.
The present embodiment and embodiment illustrated in fig. 1 difference lies in, step 202 determine fresh information push object it
Afterwards, the file destination after renewal can be sent to identified push object.
It should be noted that step 203 and step 204 are limited without stringent execution sequence, step 203 can be in step
Performed before 204, can also after step 204 perform, can also be performed at the same time with step 204.
, can be first to step 202 institute after file destination after server end is successfully received renewal in specific application
Definite push object sends the file destination after renewal, after file destination after each push object is properly received renewal,
The information of the push Object Push file renewal determined again to step 202.File is received in the push object that step 202 determines more
After new information, renewal file destination can be selected to ignore this document fresh information to latest edition, continue to access more
File destination before new.
It should be noted that since server end to push object when sending the file destination after renewal, can be rear
Platform carries out, so as to avoid bothering the normal use of push object user, for example, the file destination after can this be updated is stored in
In the caching for pushing object, so when selection updates file destination to latest edition, the file destination after renewal can be quick
Show.
After file destination after server end is successfully received renewal, if step 203 and step 204 perform at the same time, and
When pushing Object Selection renewal file destination to latest edition, since server end has begun to the target after active push renewal
File, so what the file destination after renewal can also be faster shows.
In addition, after the file destination that server end is successfully received after renewal, if step 203 is held after step 204
OK, when and push Object Selection updates file destination to latest edition, since server end is pushing file destination renewal letter
After breath, it is not necessary in the case of pushing Object Selection, the file destination after active push renewal is had begun to, so after renewal
File destination can also be faster show.
As seen from the above, after the message that received server-side is updated to file destination, server end can be with active push
The fresh information of file destination and file destination after renewal, so that client can know the information of file renewal in time,
And the file after renewal can be enabled quickly to be showed in client, obtain preferable user experience effect.
Fig. 3 is a kind of file update information pusher structure diagram provided in an embodiment of the present invention, which includes：
File is updated message reception module 301, client determining module 302 and file update information pushing module 303.
Wherein, file is updated message reception module 301, the message being updated for receiving file destination；
Client determining module 302, in having the client of requirements for access to the file destination, determining renewal letter
The push object of breath；
File update information pushing module 303, for the renewal to file destination described in identified push Object Push
Information.
In the present embodiment, client determining module 302 can be specifically used for determining receiving what file destination was updated
Before message, the client of the file destination is being accessed.
Wherein, client determining module 302 can include：First determination sub-module and the second determination sub-module（In figure not
Show）.First determination sub-module, for determining all clients for accessing file destination；Second determination sub-module, for
In the definitive result of first determination sub-module, determine before the message that file destination is updated is received, accessing mesh
Mark the client of file.
In the present embodiment, file update information pushing module 303 can be specifically used for identified client push bag
Include the mark of file destination, the client identification for updating file destination, renewal time and/or the renewal for updating synopsis information
Information.
As seen from the above, in this programme after the message that received server-side to file destination is updated, by there is visit
Ask the mode of the client push fresh information of file destination demand so that each client can timely know this document quilt
The message of renewal.
Fig. 4 is another file update information pusher structure diagram provided in an embodiment of the present invention, the device bag
Include：Data transmission blocks 403 and file be more after file is updated message reception module 401, client determining module 402, renewal
New information pushing module 404.
It should be noted that in embodiment illustrated in fig. 4, file is updated message reception module 401, client determining module
402 and file update information pushing module 404, message sink mould can be updated respectively at the file in embodiment illustrated in fig. 3
Block 301, client determining module 302 are identical with file update information pushing module 303, therefore, are not repeated herein.
In the present embodiment, data transmission blocks 403 after renewal, for determining fresh information in the client determining module
Push object after, to it is identified push object send renewal after file destination.
As seen from the above, after the message that received server-side is updated to file destination, after server end first updates this
File destination send to each and have the client of access target file demand, then information push is updated, so that client
End can know the information of file renewal in time, and the file after renewal can be enabled quickly to be showed in client,
Preferable user experience effect is obtained.
For device embodiment, since it is substantially similar to embodiment of the method, so description is fairly simple, it is related
Part illustrates referring to the part of embodiment of the method.
It should be noted that herein, relational terms such as first and second and the like are used merely to a reality
Body or operation are distinguished with another entity or operation, are deposited without necessarily requiring or implying between these entities or operation
In any this actual relation or order.Moreover, term " comprising ", "comprising" or its any other variant are intended to
Non-exclusive inclusion, so that process, method, article or equipment including a series of elements not only will including those
Element, but also including other elements that are not explicitly listed, or further include as this process, method, article or equipment
Intrinsic key element.In the absence of more restrictions, the key element limited by sentence "including a ...", it is not excluded that
Also there are other identical element in process, method, article or equipment including the key element.
Can one of ordinary skill in the art will appreciate that realizing that all or part of step in above method embodiment is
To instruct relevant hardware to complete by program, the program can be stored in computer read/write memory medium,
The storage medium designated herein obtained, such as：ROM/RAM, magnetic disc, CD etc..
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the scope of the present invention.It is all
Any modification, equivalent replacement, improvement and so within the spirit and principles in the present invention, are all contained in protection scope of the present invention
It is interior.
Claims (8)
- A kind of 1. file update information method for pushing, it is characterised in that the described method includes：Receive the message that file destination is updated；In having the client of requirements for access to the file destination, the push object of fresh information is determined；To the file destination and the fresh information of the file destination after identified push object active push renewal, institute Stating the file destination after renewal can be：Server end is updated the time sequencing of message according to file destination is received, and will connect File destination between time receiving after newest renewal, is determined as the file destination of latest edition.
- It is 2. according to the method described in claim 1, it is characterized in that, described in the client for having requirements for access to the file destination In end, determine the push object of fresh information, be：Determine before the message that file destination is updated is received, accessing the client of the file destination.
- 3. the according to the method described in claim 2, it is characterized in that, message for determining to be updated in reception file destination Before, the client of the file destination is being accessed, including：Determine all clients for accessing file destination；The client of file destination was accessed all, determines before the message that file destination is updated is received, is visiting Ask the client of file destination.
- 4. according to the method described in claim 1, it is characterized in that, the fresh information, including：The mark of file destination, the client identification for updating file destination, renewal time and/or renewal synopsis information.
- 5. a kind of file update information pusher, it is characterised in that described device includes：File is updated message reception module, the message being updated for receiving file destination；Client determining module, in having the client of requirements for access to the file destination, determining pushing away for fresh information Send object；File update information pushing module, for it is identified push Object Push described in file destination fresh information；Data transmission blocks after renewal, for after the client determining module determines the push object of fresh information, actively The file destination after renewal is sent to identified push object, the file destination after the renewal can be：Server end is pressed According to the time sequencing for receiving file destination and being updated message, the file destination after the newest renewal of receiving time is determined as The file destination of latest edition.
- 6. device according to claim 5, it is characterised in that the client determining module, specifically for determining connecing Before receiving the message that file destination is updated, the client of the file destination is being accessed.
- 7. device according to claim 6, it is characterised in that the client determining module, including：First determines submodule Block and the second determination sub-module；First determination sub-module, for determining all clients for accessing file destination；Second determination sub-module, in the definitive result of first determination sub-module, determining receiving target Before the message that file is updated, the client just in access target file.
- 8. device according to claim 5, it is characterised in that the file update information pushing module, specifically for The mark of identified client push including file destination, the client identification for updating file destination, renewal time and/or more The fresh information of new content summary info.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310589829.5A CN103595808B (en) | 2013-11-20 | 2013-11-20 | A kind of file update information method for pushing and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310589829.5A CN103595808B (en) | 2013-11-20 | 2013-11-20 | A kind of file update information method for pushing and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103595808A CN103595808A (en) | 2014-02-19 |
| CN103595808B true CN103595808B (en) | 2018-04-24 |
Family
ID=50085787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310589829.5A Active CN103595808B (en) | 2013-11-20 | 2013-11-20 | A kind of file update information method for pushing and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103595808B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104702703B (en) * | 2015-03-30 | 2019-03-15 | 北京奇艺世纪科技有限公司 | A kind of data-updating method and device |
| WO2016192030A1 (en) * | 2015-06-01 | 2016-12-08 | 阮元 | Patent information push method during product update alerts and information alert system |
| WO2016192115A1 (en) * | 2015-06-05 | 2016-12-08 | 阮元 | File update alert method and information alert system |
| CN105183815A (en) * | 2015-08-27 | 2015-12-23 | 北京恒华伟业科技股份有限公司 | Multiuser file operation method and apparatus |
| CN107357691B (en) * | 2016-05-09 | 2022-06-21 | 中兴通讯股份有限公司 | Method and device for processing mirror image file |
| CN107704537A (en) * | 2017-09-22 | 2018-02-16 | 咪咕动漫有限公司 | A kind of dissemination method, device and the storage medium of object to be updated |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102111344A (en) * | 2009-12-29 | 2011-06-29 | 腾讯科技（深圳）有限公司 | Method for reminding business updating and device adopting same |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101729441B (en) * | 2008-11-03 | 2011-12-07 | 华为技术有限公司 | Update reminding method, system thereof, update source server and access server |
-
2013
- 2013-11-20 CN CN201310589829.5A patent/CN103595808B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102111344A (en) * | 2009-12-29 | 2011-06-29 | 腾讯科技（深圳）有限公司 | Method for reminding business updating and device adopting same |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103595808A (en) | 2014-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103595808B (en) | A kind of file update information method for pushing and device | |
| CN103457993B (en) | Local cache device and the method that content caching service is provided | |
| US20170249328A1 (en) | A Method, Cloud Synchronization Function Means and File System for Handling Files and Directories in a Cloud Storage Service | |
| KR101028639B1 (en) | Managed object replication and delivery | |
| US10313452B2 (en) | Migrating a chat message service provided by a chat server to a new chat server | |
| US20100161752A1 (en) | Method and System of Administrating a Peer-to-Peer File Sharing Network | |
| US9549036B2 (en) | Network injected storage redirection for embedded applications | |
| CN108121783A (en) | A kind of automatic cleaning method, device, computer and storage medium for storing data | |
| US9356985B2 (en) | Streaming video to cellular phones | |
| CN111447248A (en) | File transmission method and device | |
| CN104410660A (en) | Method and device of downloading multimedia resources as well as router and server | |
| CN104717314A (en) | IP management method and system, client-side and server | |
| CN108347459A (en) | A kind of high in the clouds data quick storage method and device | |
| CN105450682A (en) | Method, device, and system for data synchronous storage and synchronizing data to client | |
| US7953822B2 (en) | Method of and apparatus for downloading data | |
| US20100332506A1 (en) | Marking sought after content items on network media devices | |
| CN111176706A (en) | Terminal upgrading method and device, electronic equipment and storage medium | |
| CN105897833A (en) | Advertisement data processing method and router | |
| EP3384642A1 (en) | Forwarding table compression | |
| CN104243469A (en) | Playing control method, device and system | |
| CN111131498B (en) | URL information updating method, cache server, equipment and storage medium | |
| CN111083160A (en) | Resource information recovery method and device | |
| CN105872634A (en) | Video data sharing method and device | |
| US10798147B2 (en) | Constraint based controlled seeding | |
| CN103795810A (en) | Data distribution system and method and central server of data distribution system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: Jinshan software building No. 8 Jingshan Hill Road, Lane 519015 Lianshan Jida Zhuhai city in Guangdong Province Applicant after: Zhuhai Kingsoft Office Software Co., Ltd. Applicant after: Beijing Kingsoft office software Limited by Share Ltd Address before: Jinshan software building No. 8 Jingshan Hill Road, Lane 519015 Lianshan Jida Zhuhai city in Guangdong Province Applicant before: Zhuhai Kingsoft Office Software Co., Ltd. Applicant before: Beijing Kingsoft WPS Office Co., Ltd. |
|
| COR | Change of bibliographic data | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CB03 | Change of inventor or designer information | ||
| CB03 | Change of inventor or designer information |
Inventor after: Chao Yuntong Inventor after: Ou Dizuo Inventor after: Huang Zhishou Inventor after: Huang Xupeng Inventor after: Hong Xuewen Inventor after: Liu Huan Inventor after: Li Yafei Inventor after: Fang Ting Inventor before: Chao Yuntong Inventor before: Ou Dizuo Inventor before: Huang Zhishou Inventor before: Huang Xupeng Inventor before: Hong Xuewen Inventor before: Liu Huan Inventor before: Li Yafei Inventor before: Fang Ting |