CN105808731A - Data storage method and device - Google Patents
Data storage method and device Download PDFInfo
- Publication number
- CN105808731A CN105808731A CN201610134152.XA CN201610134152A CN105808731A CN 105808731 A CN105808731 A CN 105808731A CN 201610134152 A CN201610134152 A CN 201610134152A CN 105808731 A CN105808731 A CN 105808731A
- Authority
- CN
- China
- Prior art keywords
- cookie
- record
- stored
- attribute information
- afoul
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a data storage method and device. The method comprises the following steps: obtaining a received Cookie record to be stored; comparing the Cookie record to be stored with a prestored Cookie record to judge whether the action scope of the Cookie record to be stored and the action scope of the prestored Cookie record mutually conflict or not; and according to a judgment result, determining whether the Cookie record to be stored is stored or not. The technical scheme can compare the Cookie record to be stored with the prestored Cookie record to automatically and accurately judge whether the action scope of the Cookie record to be stored and the action scope of the prestored Cookie record mutually conflict or not so as to avoid a phenomenon that the action scopes of Cookie conflict by extremely low cost.
Description
Technical field
It relates to technical field of data processing, particularly relate to date storage method and device.
Background technology
In the related, http agreement (HyperTextTransferProtocol, HTML (Hypertext Markup Language)) is stateless, and each http request is all independent of each other.And Cookie is (sometimes also with its plural form Cookies, refer to that some website is in order to distinguish user identity, carry out session tracking and be stored in the data on user local terminal) effect exactly the status data of user is stored in client, these data send to server along with each http request, server, by resolving these Cookie data, learns the state of client.But, along with developing of company size, support company runs and the Web subsystem of business will get more and more, and these Web subsystems are usually deployed under the same parent domain name of company, thus may result in two subsystems and the afoul phenomenon of Cookie action scope occur.Such as: assume there are following two subsystems, Web subsystem A, domain name a.company.com, need to domain name company.com, path/lower write foo by name, be worth the Cookie for value, user have accessed subsystem A, receive the Cookie of subsystem A write, then user removes access sub-system B again, but owing to b.company.com is the subdomain name of company.com, the Cookie belonging to subsystem A has been sent to subsystem B by browser, subsystem B reads the data being not belonging to native system, causes that program occurs abnormal.
Summary of the invention
Disclosure embodiment provides date storage method and device.Described technical scheme is as follows:
First aspect according to disclosure embodiment, it is provided that a kind of date storage method, including:
Obtain the Cookie record to be stored received；
The Cookie record of described Cookie to be stored record with pre-stored is compared, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
According to judged result, it is determined whether described Cookie to be stored record is stored.
In one embodiment, the described Cookie record by described Cookie to be stored record with pre-stored compares, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, including:
The attribute information that the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
In one embodiment, described the attribute information that the Cookie of described Cookie to be stored attribute information and the pre-stored recorded records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, including:
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
In one embodiment, described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
In one embodiment, described according to judged result, it is determined whether described Cookie to be stored is stored, including:
When there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded during described Cookie to be stored records, a described afoul Cookie record is pointed out to store unsuccessfully；
When described Cookie to be stored is absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record in recording, all of described Cookie to be stored record is stored.
In one embodiment, described method also includes:
When pointing out a described afoul Cookie record to store unsuccessfully, the attribute information of a described afoul Cookie record is displayed.
In one embodiment, described method also includes:
When being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
Second aspect according to disclosure embodiment, it is provided that a kind of data storage device, including:
Acquisition module, for obtaining the Cookie record to be stored received；
Judge module, for comparing the Cookie record of described Cookie to be stored record with pre-stored, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
Determine module, for according to judged result, it is determined whether stored by described Cookie to be stored record.
In one embodiment, described judge module includes:
Comparison sub-module, for the attribute information that the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
In one embodiment, described comparison sub-module is additionally operable to:
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
In one embodiment, described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
In one embodiment, described determine that module includes:
Prompting submodule, during for there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded as described Cookie to be stored in recording, points out a described afoul Cookie record to store unsuccessfully；
Sub module stored, during for being absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record as described Cookie to be stored in recording, stores all of described Cookie to be stored record.
In one embodiment, described device also includes:
Display module, for when pointing out a described afoul Cookie record to store unsuccessfully, displaying the attribute information of a described afoul Cookie record.
In one embodiment, described device also includes:
Reminding module, for when being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
The third aspect according to disclosure embodiment, it is provided that a kind of data storage device, including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
Obtain the Cookie record to be stored received；
The Cookie record of described Cookie to be stored record with pre-stored is compared, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
According to judged result, it is determined whether described Cookie to be stored record is stored.
Embodiment of the disclosure that the technical scheme of offer can include following beneficial effect:
The technical scheme of offer is provided, when getting Cookie to be stored record, the Cookie record of Cookie to be stored record with pre-stored can be compared, with automatically, judge whether the Cookie to be stored action scope recorded conflicts mutually with the Cookie of the pre-stored action scope recorded exactly, thus avoiding the afoul generation of Cookie action scope with minimum cost, guarantee only will not store with the afoul Cookie to be stored record of the Cookie of the pre-stored action scope recorded, to avoid the afoul Cookie record of the action scope in being recorded by Cookie to be stored to be stored in data base, and cause that this corresponding Cookie record in the Cookie record of pre-stored is capped.
It should be appreciated that it is only exemplary and explanatory that above general description and details hereinafter describe, the disclosure can not be limited.
Accompanying drawing explanation
Accompanying drawing herein is merged in description and constitutes the part of this specification, it is shown that meets and embodiment of the disclosure, and for explaining the principle of the disclosure together with description.
Fig. 1 is the flow chart of a kind of date storage method according to an exemplary embodiment.
Fig. 2 is the flow chart of the another kind of date storage method according to an exemplary embodiment.
Fig. 3 is the flow chart of another date storage method according to an exemplary embodiment one.
Fig. 4 is the flow chart of another date storage method according to an exemplary embodiment one.
Fig. 5 is the flow chart of another date storage method according to an exemplary embodiment one.
Fig. 6 is the flow chart of another date storage method according to an exemplary embodiment one.
Fig. 7 is the block diagram of a kind of data storage device according to an exemplary embodiment.
Fig. 8 is the block diagram of the another kind of data storage device according to an exemplary embodiment.
Fig. 9 is the block diagram of another data storage device according to an exemplary embodiment.
Figure 10 is the block diagram of another data storage device according to an exemplary embodiment.
Figure 11 is the block diagram of another data storage device according to an exemplary embodiment.
Figure 12 is the block diagram being applicable to data storage device according to an exemplary embodiment.
Detailed description of the invention
Here in detail exemplary embodiment being illustrated, its example representation is in the accompanying drawings.When as explained below relates to accompanying drawing, unless otherwise indicated, the same numbers in different accompanying drawings represents same or analogous key element.Embodiment described in following exemplary embodiment does not represent all embodiments consistent with the disclosure.On the contrary, they only with in appended claims describe in detail, the disclosure some in the example of consistent apparatus and method.
In the related, http agreement (HyperTextTransferProtocol, HTML (Hypertext Markup Language)) is stateless, and each http request is all independent of each other.And Cookie is (sometimes also with its plural form Cookies, refer to that some website is in order to distinguish user identity, carry out session tracking and be stored in the data on user local terminal) effect exactly the status data of user is stored in client, these data send to server along with each http request, server, by resolving these Cookie data, learns the state of client.But, along with developing of company size, support company runs and the Web subsystem of business will get more and more, and these Web subsystems are usually deployed under the same parent domain name of company, thus may result in two subsystems and the afoul phenomenon of Cookie action scope occur.Such as: assume there are following two subsystems, Web subsystem A, domain name a.company.com, need to domain name company.com, path/lower write foo by name, be worth the Cookie for value, user have accessed subsystem A, receive the Cookie of subsystem A write, then user removes access sub-system B again, but owing to b.company.com is the subdomain name of company.com, the Cookie belonging to subsystem A has been sent to subsystem B by browser, subsystem B reads the data being not belonging to native system, causes that program occurs abnormal.
In order to solve above-mentioned technical problem, disclosure embodiment provides a kind of date storage method, and the method can be used in data recording program, system or device, and executive agent corresponding to the method can be the terminal that user carries, as it is shown in figure 1, the method comprising the steps of S101 to step S103:
In step S101, obtain the Cookie record to be stored received；
Cookie to be stored record can be that the Cookie being pre-stored in data base records, can also be a plurality of Cookie record, the content of its record can be the logon information of certain account of user, can also be the various information such as the information of certain application program, or the information of system.
In step s 102, the Cookie record of Cookie to be stored record with pre-stored is compared, it is judged that whether Cookie to be stored record conflicts mutually with the Cookie of the pre-stored action scope recorded；
By the Cookie record of Cookie to be stored record with pre-stored is compared, it is possible to carry out collision detection automatically, exactly, namely judge whether the Cookie to be stored action scope recorded conflicts mutually with the Cookie of the pre-stored action scope recorded.
In step s 103, according to judged result, it is determined whether Cookie to be stored record is stored.
When the action scope of a certain Cookie record during Cookie to be stored records with a certain Cookie record in the Cookie record of pre-stored in data base is conflicted mutually, illustrate that these two Cookie records can cover mutually, if namely this Cookie to be stored is recorded in write into Databasce by user, the Cookie record stored will be covered, make the Cookie record that developer or user cannot store before normally reading, thus, when action scope is conflicted mutually, this Cookie record to be stored can not be stored, thus avoiding the afoul generation of Cookie action scope with minimum cost；Otherwise, if the action scope that the action scope of the every Cookie record in this Cookie to be stored record records with the every Cookie in the Cookie record of pre-stored in data base does not all collide, then illustrate that the every Cookie record in this Cookie to be stored record all will not cover the every Cookie record in the Cookie record of this pre-stored, then Cookie to be stored record is stored in data base, so that during to server transmission http request, the Cookie record stored in user side can be sent to server, mounted application program in the User Status of user side and/or user side is accurately understood for server, the state of system.
As in figure 2 it is shown, in one embodiment, above-mentioned steps S102 can be performed as:
In step A1, the attribute information that the Cookie of the Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether Cookie to be stored record conflicts mutually with the Cookie of the pre-stored action scope recorded, wherein, attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
The attribute information of the attribute information of Cookie to be stored record and the Cookie record of pre-stored includes the one or more information in the action path (i.e. CookiePath) of the record number of its affiliated Cookie record, the project name of its affiliated Cookie record, the cookie name word (i.e. CookieName) of its affiliated Cookie record, the domain name (i.e. CookieDomain) of its affiliated Cookie record, its affiliated Cookie record respectively；
nullAnd the action scope of Cookie record depends primarily on CookieName、These three information of CookieDomain and CookiePath，Thus，These three information are the whether afoul determinant attribute information of action scope determining two Cookie records，So，When the attribute information that the Cookie of the Cookie to be stored attribute information recorded with pre-stored records is compared，Need the CookieName recorded of the every Cookie in being recorded by Cookie to be stored emphatically、CookieDomain and CookiePath，The CookieName of the every Cookie record in recording with the Cookie of pre-stored、CookieDomain and CookiePath compares，To judge whether a certain Cookie record in Cookie to be stored record conflicts (namely whether action scope scope is identical) mutually with the action scope of a certain Cookie record in the Cookie of pre-stored record.
As it is shown on figure 3, in one embodiment, above-mentioned steps A1 can be performed as:
In step bl is determined., the attribute information of the every Cookie record in being recorded by Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of pre-stored record respectively；
In step B2, when the attribute information of the Cookie record during Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of pre-stored meet and preset conflict condition, it is determined that a Cookie record conflicts mutually with the action scope of the 2nd Cookie record；
nullWhen judging whether Cookie to be stored record (action scope) conflicts mutually with the Cookie of the pre-stored action scope recorded，Need to judge item by item，That is: the attribute information of the every Cookie record in being recorded by Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of pre-stored record item by item respectively，When the attribute information of certain the Cookie record during Cookie to be stored records meets this default conflict condition with the attribute information of certain the 2nd Cookie record in the Cookie record of pre-stored，Judge that the i.e. action scope identical with the action scope scope of the 2nd Cookie record in the Cookie of pre-stored record of the Cookie record in Cookie to be stored record is conflicted mutually，Now，The Cookie record in Cookie to be stored record is pointed out to store unsuccessfully，To point out user to do corresponding clash handle，The Cookie record in being recorded by Cookie to be stored is avoided to be stored in data base，And cause that this corresponding 2nd Cookie record in the Cookie record of pre-stored is capped；
Additionally, it should be understood that a Cookie is recorded as any one Cookie record in Cookie to be stored record, 2nd Cookie is recorded as any one Cookie record in pre-stored Cookie record, and so-called " first ", " second " is intended merely to the convenient Cookie entry distinguished in Cookie to be stored record and the Cookie entry in pre-stored Cookie record, namely a Cookie record does not represent the name of each Cookie record in Cookie to be stored record, similarly, 2nd Cookie record does not represent the name of each Cookie record in pre-stored Cookie record yet.
In step B3, when the attribute information of each Cookie record during Cookie to be stored records all is unsatisfactory for presetting conflict condition with the attribute information of each 2nd Cookie record in the Cookie of pre-stored record, judge in Cookie to be stored record and be absent from the Cookie with pre-stored to record afoul Cookie record, wherein, oneth Cookie is recorded as any one Cookie record in Cookie to be stored record, and the 2nd Cookie is recorded as any one Cookie record in pre-stored Cookie record.
nullAdditionally，When the attribute information of each Cookie record during Cookie to be stored records all is unsatisfactory for this default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of pre-stored record，Illustrate that the action scope of each item the oneth Cookie record in this Cookie to be stored record is not all conflicted with the action scope of each Cookie record in this pre-stored Cookie record mutually，When further relating to be stored in data base all item Cookie record in this Cookie to be stored record，Any one Cookie record in the Cookie record of pre-stored can't be covered，Thus，Can be determined that in Cookie to be stored record and be absent from the Cookie with pre-stored and record afoul Cookie record.
In one embodiment, default conflict condition includes:
The cookie name word of the oneth Cookie record and the cookie name word of the 2nd Cookie record are identical；And
The domain name of the oneth Cookie record is identical with the domain name that the 2nd Cookie records or father and son's domain name each other；And
The action path of the oneth Cookie record is identical with the action path that the 2nd Cookie records or father and son path each other.
Default conflict condition generallys include four kinds of conditions:
The cookie name word of the condition A: the one Cookie record and the cookie name word of the 2nd Cookie record are identical, the domain name of the oneth Cookie record is identical with the domain name that the 2nd Cookie records, and the action path of a Cookie record is identical with the action path that the 2nd Cookie records；
The cookie name word of the condition B: the one Cookie record and the cookie name word of the 2nd Cookie record are identical, the domain name of the oneth Cookie record is identical with the domain name that the 2nd Cookie records, the action path of the oneth Cookie record is with the action path father and son path each other of the 2nd Cookie record (such as: the action path of a certain Cookie record in Cookie record to be stored is the father path of the action path of a certain Cookie record in pre-stored Cookie record, or the action path of a certain Cookie record in Cookie to be stored record is the subpath of the action path of a certain Cookie record in the Cookie record of pre-stored)；
Condition C: the cookie name word of a Cookie record and the cookie name word of the 2nd Cookie record are identical, domain name father and son's domain name each other that the domain name of the oneth Cookie record records with the 2nd Cookie is (such as: the domain name of a certain Cookie record in Cookie to be stored record is the father field name of the domain name of a certain Cookie record in the Cookie record of pre-stored, or the domain name of a certain Cookie record in Cookie to be stored record is the subdomain name of the domain name of a certain Cookie record in the Cookie record of pre-stored), the action path of the oneth Cookie record and the 2nd Cookie action path father and son path each other recorded；
The cookie name word of the condition D: the one Cookie record and the cookie name word of the 2nd Cookie record are identical, the domain name of the oneth Cookie record and the 2nd Cookie domain name father and son's domain name each other recorded, the action path of a Cookie record is identical with the action path that the 2nd Cookie records；
nullWhen any one condition that the attribute information of certain Cookie record during Cookie to be stored records meets in above-mentioned four kinds of conditions with the attribute information recorded of certain the 2nd Cookie in the Cookie record of pre-stored，Judge that the i.e. action scope identical with the action scope scope of the 2nd Cookie record in the Cookie of pre-stored record of the Cookie record in Cookie to be stored record is conflicted mutually，Now，The Cookie record in Cookie to be stored record is pointed out to store unsuccessfully，To point out user to do corresponding clash handle，The Cookie record in being recorded by Cookie to be stored is avoided to be stored in data base，And cause that the 2nd Cookie record in the Cookie record of pre-stored is capped.
Will be exemplified below, the whether afoul judge process of action scope that the action scope of Cookie to be stored record and pre-stored Cookie record:
1, the every Cookie record in pre-stored Cookie record in tentation data storehouse, as shown in table 1:
Table 1
2, the every Cookie record in Cookie record to be stored is assumed, as shown in table 2:
Table 2
| Put on record item | Put on record request 1 | Put on record request 2 | Put on record request 3 | Put on record request 4 |
| Project | App_x | App_x | App_x | App_x |
| CookieName | ca | ca | cc | cd |
| CookieDomain | .company.com | a.company.com | x.company.com | x.company.com |
| CookiePath | / | /x | / | / |
3, during the every Cookie record in storing this Cookie to be stored record, the attribute information (i.e. CookieName, CookieDomain, CookiePath) needing the record of the every Cookie in being recorded by the Cookie to be stored in table 2 compares with the attribute information of every Cookie record in the Cookie record of pre-stored in table 1 respectively, and concrete comparison procedure is as follows:
Step a), the data consistent for CookieName that in table 1, all Cookiename submit to are obtained with table 2 from data base, if taking less than data, then all Cookie in table 2 are recorded write into Databasce, successfully prompting of putting on record is returned to user, and it is true that ask shown in 1 according to putting on record in table 2, taking out CookieName from data base is the data record #1 and data record #4 of ca, and takes out the identical record of CookieName from table 1 according to the request of putting on record of other in table 2 successively；
Cookie record consistent with the CookieName that step a) takes out successively for CookieDomain in step b), the Cookie submitted to by table 2 record carries out detection as follows:
Judge the CookieDomain recorded of the Cookie consistent with the CookieName that step a) takes out for CookieDomain in the Cookie record that table 2 submits to whether unanimously or each other father and son's domain name；If it is judged that be false, then carry out collision detection with next data；If result is true, then judge that whether consistent with the CookiePath recording each Cookie record in table 1 CookiePath that the result that table 2 is submitted to is genuine Cookie record or father and son path each other；If result is true, this result in the Cookie record then submitted to by table 2 is stored in conflict item list for really recording id, until all item Cookie record that table 2 is submitted to has carried out collision detection, if this conflict item list is empty, the action scope of each Cookie record in all item Cookie record that then explanation table 2 is submitted to is not all conflicted with the action scope of the Cookie record of pre-stored in table 1 mutually, the all item Cookie that then can be submitted to by table 2 record write into Databasce, return to put on record to user and successfully point out；Otherwise return the afoul conflict item list of action scope to user, and point out the Cookie record in these conflict item lists of user to put on record unsuccessfully.And specific to the table 1 in the present embodiment and table 2, after collision detection, following result can obtained:
The action scope of the request 1 of putting on record in table 2 clashes with the action scope of put on record record #1 and the record #4 that puts on record of record in table 1 in current database；
The action scope of the request 2 of putting on record in table 2 clashes with the action scope of the record #1 that puts on record of record in table 1 in current database；
The action scope of the request 3 of putting on record in table 2 clashes with the action scope of the record #5 that puts on record of record in table 1 in current database；
The action scope of the request 4 of putting on record in table 2 does not clash with any action scope putting record on record of record in table in current database 1, and this is put on record and submits to successfully.
As shown in Figure 4, in one embodiment, above-mentioned steps S103 can be performed as:
In step C1, when there is a Cookie record afoul with the Cookie of the pre-stored action scope recorded during Cookie to be stored records, an afoul Cookie record is pointed out to store unsuccessfully；
In step C2, when Cookie to be stored record being absent from the afoul Cookie of the action scope recorded of the Cookie with pre-stored and recording, all of Cookie to be stored record is stored.
When there is a Cookie record of conflict mutually with the action scope that the Cookie of pre-stored records (namely action scope scope is identical) in recording in this Cookie to be stored, this afoul Cookie record is pointed out to store unsuccessfully, to point out user to carry out clash handle, avoid this afoul Cookie record in being recorded by Cookie to be stored to be stored in data base, and cause that in the Cookie record of pre-stored, corresponding 2nd Cookie record is capped；
When Cookie to be stored record being absent from the afoul Cookie of the action scope recorded of the Cookie with pre-stored and recording, illustrate when the record of each Cookie in being recorded by this Cookie to be stored stores to data base, all will not cover any Cookie record stored, thus, directly all of Cookie to be stored record is stored.
As it is shown in figure 5, in one embodiment, method also includes:
In step S501, when pointing out an afoul Cookie record to store unsuccessfully, the attribute information of an afoul Cookie record is displayed.
When pointing out this afoul Cookie record to store unsuccessfully, by the attribute information of this afoul Cookie record is displayed, the Cookie record that user can be pointed out to be stored conflicts mutually with the action scope of which Cookie record of which project in the Cookie record stored, to realize evading the afoul purpose of Cookie action scope.
As shown in Figure 6, in one embodiment, method also includes:
In step s 601, when being displayed by the attribute information of an afoul Cookie record, prompting is revised the cookie name word of an afoul Cookie record or points out the cookie name word of twoth Cookie record afoul with the afoul Cookie action scope recorded in amendment pre-stored Cookie record.
Due to Cookie record domain name and what action path will not be modified often easily, such as a certain Cookie record must be stored under certain path in the terminal of certain domain name, thus, when the attribute information of this afoul Cookie record is displayed so that user to be pointed out, user can be pointed out to revise the CookieName of this afoul Cookie record, or with afoul 2nd Cookie of action scope of this afoul Cookie record cookie name word recorded in pointing out the Cookie that user revises pre-stored to record, to realize evading the afoul purpose of Cookie action scope.
The above-mentioned date storage method that corresponding disclosure embodiment provides, disclosure embodiment also provides for a kind of data storage device, as it is shown in fig. 7, this device includes:
Acquisition module 701, is configured to obtain the Cookie record to be stored received；
Judge module 702, is configured to the Cookie record by described Cookie to be stored record with pre-stored and compares, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
Determine module 703, be configured to according to judged result, it is determined whether described Cookie to be stored record is stored.
As shown in Figure 8, in one embodiment, described judge module 702 includes:
Comparison sub-module 7021, it is configured to the attribute information by the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records compare, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
In one embodiment, described comparison sub-module 7021 is also configured to
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
In one embodiment, described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
As it is shown in figure 9, in one embodiment, described determine that module 703 includes:
Prompting submodule 7031, when being configured as there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded in described Cookie to be stored record, points out a described afoul Cookie record to store unsuccessfully；
Sub module stored 7032, when being configured as being absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record in described Cookie to be stored record, stores all of described Cookie to be stored record.
As shown in Figure 10, in one embodiment, described device also includes:
Display module 1001, is configured to, when pointing out a described afoul Cookie record to store unsuccessfully, be displayed by the attribute information of a described afoul Cookie record.
As shown in figure 11, in one embodiment, described device also includes:
Reminding module 1101, being configured to when being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
The third aspect according to disclosure embodiment, it is provided that a kind of data storage device, including:
Processor；
For the memorizer for storing processor executable；
Wherein, processor is configured to:
Obtain the Cookie record to be stored received；
The Cookie record of described Cookie to be stored record with pre-stored is compared, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
According to judged result, it is determined whether described Cookie to be stored record is stored.
Above-mentioned processor is also configured to:
The described Cookie record by described Cookie to be stored record with pre-stored compares, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, including:
The attribute information that the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
Above-mentioned processor is also configured to:
Described the attribute information that the Cookie of described Cookie to be stored attribute information and the pre-stored recorded records is compared, whether conflict mutually with the Cookie of the described pre-stored action scope recorded judging that described Cookie to be stored records, including:
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
Above-mentioned processor is also configured to:
Described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
Above-mentioned processor is also configured to:
Described according to judged result, it is determined whether described Cookie to be stored is stored, including:
When there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded during described Cookie to be stored records, a described afoul Cookie record is pointed out to store unsuccessfully；
When described Cookie to be stored is absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record in recording, all of described Cookie to be stored record is stored.
Above-mentioned processor is also configured to:
Described method also includes:
When pointing out a described afoul Cookie record to store unsuccessfully, the attribute information of a described afoul Cookie record is displayed.
Above-mentioned processor is also configured to:
Described method also includes:
When being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
Figure 12 is a kind of block diagram for data storage device 1200 according to an exemplary embodiment, and this device is applicable to terminal unit.Such as, device 1200 can be mobile phone, computer, digital broadcast terminal, messaging devices, game console, tablet device, armarium, body-building equipment, personal digital assistant etc..
With reference to Figure 12, device 1200 can include with next or at least two assembly: processes assembly 1202, memorizer 1204, power supply module 1206, multimedia groupware 1208, audio-frequency assembly 1210, the interface 1212 of input/output (I/O), sensor cluster 1214, and communications component 1216.
Process assembly 1202 and generally control the integrated operation of device 1200, such as with display, call, data communication, the operation that camera operation and record operation are associated.Process assembly 1202 and can include one or at least two processor 1220 to perform instruction, to complete all or part of step of above-mentioned method.Additionally, process assembly 1202 can include one or at least two module, it is simple to what process between assembly 1202 and other assemblies is mutual.Such as, process assembly 1202 and can include multi-media module, with facilitate multimedia groupware 1208 and process between assembly 1202 mutual.
Memorizer 1204 is configured to store various types of data to support the operation at equipment 1200.The example of these data includes any storage object for operation on device 1200 or the instruction of method, contact data, telephone book data, message, picture, video etc..Memorizer 1204 can be realized by any kind of volatibility or non-volatile memory device or their combination, such as static RAM (SRAM), Electrically Erasable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory EPROM (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, disk or CD.
The various assemblies that electric power assembly 1206 is device 1200 provide electric power.Electric power assembly 1206 can include power-supply management system, one or at least two power supply, and other generate, manage and distribute, with for device 1200, the assembly that electric power is associated.
Multimedia groupware 1208 includes the screen providing an output interface between described device 1200 and user.In certain embodiments, screen can include liquid crystal display (LCD) and touch panel (TP).If screen includes touch panel, screen may be implemented as touch screen, to receive the input signal from user.Touch panel include one or at least two touch sensor sensing touch, slide and gesture on touch panel.Described touch sensor can not only sense the border of touch or sliding action, but also detects the persistent period relevant to described touch or slide and pressure.In certain embodiments, multimedia groupware 1208 includes a front-facing camera and/or post-positioned pick-up head.When equipment 1200 is in operator scheme, during such as screening-mode or video mode, front-facing camera and/or post-positioned pick-up head can receive the multi-medium data of outside.Each front-facing camera and post-positioned pick-up head can be a fixing optical lens system or have focal length and optical zoom ability.
Audio-frequency assembly 1210 is configured to output and/or input audio signal.Such as, audio-frequency assembly 1210 includes a mike (MIC), and when device 1200 is in operator scheme, during such as call model, logging mode and speech recognition mode, mike is configured to receive external audio signal.The audio signal received can be further stored at memorizer 1204 or send via communications component 1216.In certain embodiments, audio-frequency assembly 1210 also includes a speaker, is used for exporting audio signal.
I/O interface 1212 provides interface for processing between assembly 1202 and peripheral interface module, above-mentioned peripheral interface module can be keyboard, puts striking wheel, button etc..These buttons may include but be not limited to: home button, volume button, startup button and locking press button.
Sensor cluster 1214 includes one or at least two sensor, for providing the state estimation of various aspects for device 1200.Such as, what sensor cluster 1214 can detect equipment 1200 opens/closed mode, the relative localization of assembly, such as described assembly is display and the keypad of device 1200, the position change of all right detecting device 1200 of sensor cluster 1214 or 1,200 1 assemblies of device, the presence or absence that user contacts with device 1200, the variations in temperature of device 1200 orientation or acceleration/deceleration and device 1200.Sensor cluster 1214 can include proximity transducer, is configured to when not having any physical contact object near detection.Sensor cluster 1214 can also include optical sensor, such as CMOS or ccd image sensor, for using in imaging applications.In certain embodiments, this sensor cluster 1214 can also include acceleration transducer, gyro sensor, Magnetic Sensor, pressure transducer or temperature sensor.
Communications component 1216 is configured to facilitate between device 1200 and other equipment the communication of wired or wireless mode.Device 1200 can access the wireless network based on communication standard, such as WiFi, 2G or 3G, or their combination.In one exemplary embodiment, communications component 1216 receives the broadcast singal or the broadcast related information that manage system from external broadcasting via broadcast channel.In one exemplary embodiment, described communications component 1216 also includes near-field communication (NFC) module, to promote junction service.Such as, can based on RF identification (RFID) technology in NFC module, Infrared Data Association (IrDA) technology, ultra broadband (UWB) technology, bluetooth (BT) technology and other technologies realize.
In the exemplary embodiment, device 1200 can be realized by one or at least two application specific integrated circuit (ASIC), digital signal processor (DSP), digital signal processing appts (DSPD), PLD (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic building bricks, is used for performing said method.
In the exemplary embodiment, additionally providing a kind of non-transitory computer-readable recording medium including instruction, for instance include the memorizer 1204 of instruction, above-mentioned instruction can have been performed said method by the processor 1220 of device 1200.Such as, described non-transitory computer-readable recording medium can be ROM, random access memory (RAM), CD-ROM, tape, floppy disk and optical data storage devices etc..
A kind of non-transitory computer-readable recording medium, when the instruction in described storage medium is performed by the processor of said apparatus 1200 so that said apparatus 1200 is able to carry out a kind of date storage method, including:
Obtain the Cookie record to be stored received；
The Cookie record of described Cookie to be stored record with pre-stored is compared, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
According to judged result, it is determined whether described Cookie to be stored record is stored.
In one embodiment, the described Cookie record by described Cookie to be stored record with pre-stored compares, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, including:
The attribute information that the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
In one embodiment, described the attribute information that the Cookie of described Cookie to be stored attribute information and the pre-stored recorded records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, including:
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
In one embodiment, described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
In one embodiment, described according to judged result, it is determined whether described Cookie to be stored is stored, including:
When there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded during described Cookie to be stored records, a described afoul Cookie record is pointed out to store unsuccessfully；
When described Cookie to be stored is absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record in recording, all of described Cookie to be stored record is stored.
In one embodiment, described method also includes:
When pointing out a described afoul Cookie record to store unsuccessfully, the attribute information of a described afoul Cookie record is displayed.
In one embodiment, described method also includes:
When being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
Those skilled in the art, after considering description and putting into practice disclosed herein disclosing, will readily occur to other embodiment of the disclosure.The application is intended to any modification of the disclosure, purposes or adaptations, and these modification, purposes or adaptations are followed the general principle of the disclosure and include the undocumented known general knowledge in the art of the disclosure or conventional techniques means.Description and embodiments is considered only as exemplary, and the true scope of the disclosure and spirit are pointed out by claim below.
It should be appreciated that the disclosure is not limited to precision architecture described above and illustrated in the accompanying drawings, and various amendment and change can carried out without departing from the scope.The scope of the present disclosure is only limited by appended claim.
Claims (15)
1. a date storage method, it is characterised in that including:
Obtain the Cookie record to be stored received；
The Cookie record of described Cookie to be stored record with pre-stored is compared, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
According to judged result, it is determined whether described Cookie to be stored record is stored.
2. method according to claim 1, it is characterised in that
The described Cookie record by described Cookie to be stored record with pre-stored compares, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, including:
The attribute information that the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
3. method according to claim 2, it is characterised in that
Described the attribute information that the Cookie of described Cookie to be stored attribute information and the pre-stored recorded records is compared, whether conflict mutually with the Cookie of the described pre-stored action scope recorded judging that described Cookie to be stored records, including:
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
4. method according to claim 3, it is characterised in that
Described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
5. the method according to claim 3 or 4, it is characterised in that
Described according to judged result, it is determined whether described Cookie to be stored is stored, including:
When there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded during described Cookie to be stored records, a described afoul Cookie record is pointed out to store unsuccessfully；
When described Cookie to be stored is absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record in recording, all of described Cookie to be stored record is stored.
6. method according to claim 5, it is characterised in that described method also includes:
When pointing out a described afoul Cookie record to store unsuccessfully, the attribute information of a described afoul Cookie record is displayed.
7. method according to claim 6, it is characterised in that described method also includes:
When being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
8. a data storage device, it is characterised in that including:
Acquisition module, for obtaining the Cookie record to be stored received；
Judge module, for comparing the Cookie record of described Cookie to be stored record with pre-stored, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
Determine module, for according to judged result, it is determined whether stored by described Cookie to be stored record.
9. device according to claim 8, it is characterised in that
Described judge module includes:
Comparison sub-module, for the attribute information that the Cookie of the described Cookie to be stored attribute information recorded with pre-stored records is compared, to judge whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded, wherein, described attribute information includes: at least one information in record number, project name, cookie name word, domain name and action path that affiliated Cookie records.
10. device according to claim 9, it is characterised in that
Described comparison sub-module is additionally operable to:
The attribute information of the every Cookie record in being recorded by described Cookie to be stored compares with the attribute information of the every Cookie record in the Cookie of described pre-stored record respectively；
When the attribute information of the Cookie record during described Cookie to be stored records and the attribute information of the 2nd Cookie record in the Cookie record of described pre-stored meet and preset conflict condition, it is determined that a described Cookie record conflicts mutually with the action scope of described 2nd Cookie record；
When the attribute information of each Cookie record during described Cookie to be stored records all is unsatisfactory for described default conflict condition with the attribute information of each 2nd Cookie record in the Cookie of described pre-stored record, judge in described Cookie to be stored record and be absent from recording afoul Cookie record with the Cookie of described pre-stored, wherein, a described Cookie is recorded as any one Cookie record in described Cookie to be stored record, and described 2nd Cookie is recorded as any one Cookie record in described pre-stored Cookie record.
11. device according to claim 10, it is characterised in that
Described default conflict condition includes:
The cookie name word of a described Cookie record is identical with the cookie name word of described 2nd Cookie record；And
The domain name of a described Cookie record is identical with the domain name that described 2nd Cookie records or father and son's domain name each other；And
The action path of a described Cookie record is identical with the action path that described 2nd Cookie records or father and son path each other.
12. the device according to claim 10 or 11, it is characterised in that
Described determine that module includes:
Prompting submodule, during for there is a Cookie record afoul with the Cookie of the described pre-stored action scope recorded as described Cookie to be stored in recording, points out a described afoul Cookie record to store unsuccessfully；
Sub module stored, during for being absent from an afoul Cookie record with the action scope of the Cookie of described pre-stored record as described Cookie to be stored in recording, stores all of described Cookie to be stored record.
13. device according to claim 12, it is characterised in that described device also includes:
Display module, for when pointing out a described afoul Cookie record to store unsuccessfully, displaying the attribute information of a described afoul Cookie record.
14. device according to claim 13, it is characterised in that described device also includes:
Reminding module, for when being displayed by the attribute information of a described afoul Cookie record, the cookie name word in described pre-stored Cookie record with the afoul 2nd Cookie record of action scope of a described afoul Cookie record is revised in the cookie name word of the described afoul Cookie record of prompting amendment or prompting.
15. a data storage device, it is characterised in that including:
Processor；
For storing the memorizer of processor executable；
Wherein, described processor is configured to:
Obtain the Cookie record to be stored received；
The Cookie record of described Cookie to be stored record with pre-stored is compared, it is judged that whether described Cookie to be stored record conflicts mutually with the Cookie of the described pre-stored action scope recorded；
According to judged result, it is determined whether described Cookie to be stored record is stored.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610134152.XA CN105808731A (en) | 2016-03-09 | 2016-03-09 | Data storage method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610134152.XA CN105808731A (en) | 2016-03-09 | 2016-03-09 | Data storage method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105808731A true CN105808731A (en) | 2016-07-27 |
Family
ID=56468087
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610134152.XA Pending CN105808731A (en) | 2016-03-09 | 2016-03-09 | Data storage method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105808731A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108388657A (en) * | 2018-03-06 | 2018-08-10 | 五八有限公司 | Cookie storage methods, device, equipment and readable storage medium storing program for executing |
| CN110019057A (en) * | 2017-09-27 | 2019-07-16 | 华为技术有限公司 | Request processing method and device |
| CN110737985A (en) * | 2019-10-15 | 2020-01-31 | 上海联影医疗科技有限公司 | Running data verification method and device, computer equipment and readable storage medium |
| CN112104703A (en) * | 2020-08-18 | 2020-12-18 | 厦门网宿有限公司 | Cookie management method, intermediate node and webvpn system |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039317A (en) * | 2006-03-14 | 2007-09-19 | 中兴通讯股份有限公司 | Method for realizing browse service COOKIE of wireless application protocol gateway |
| CN102638581A (en) * | 2012-03-31 | 2012-08-15 | 奇智软件（北京）有限公司 | Cookie information storage method and cookie information storage system |
| CN103532920A (en) * | 2012-07-06 | 2014-01-22 | 腾讯科技（深圳）有限公司 | Cookie update method and cookie update system |
-
2016
- 2016-03-09 CN CN201610134152.XA patent/CN105808731A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101039317A (en) * | 2006-03-14 | 2007-09-19 | 中兴通讯股份有限公司 | Method for realizing browse service COOKIE of wireless application protocol gateway |
| CN102638581A (en) * | 2012-03-31 | 2012-08-15 | 奇智软件（北京）有限公司 | Cookie information storage method and cookie information storage system |
| CN103532920A (en) * | 2012-07-06 | 2014-01-22 | 腾讯科技（深圳）有限公司 | Cookie update method and cookie update system |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110019057A (en) * | 2017-09-27 | 2019-07-16 | 华为技术有限公司 | Request processing method and device |
| CN108388657A (en) * | 2018-03-06 | 2018-08-10 | 五八有限公司 | Cookie storage methods, device, equipment and readable storage medium storing program for executing |
| CN108388657B (en) * | 2018-03-06 | 2022-04-05 | 五八有限公司 | Cookie storage method, device, equipment and readable storage medium |
| CN110737985A (en) * | 2019-10-15 | 2020-01-31 | 上海联影医疗科技有限公司 | Running data verification method and device, computer equipment and readable storage medium |
| CN112104703A (en) * | 2020-08-18 | 2020-12-18 | 厦门网宿有限公司 | Cookie management method, intermediate node and webvpn system |
| WO2022036833A1 (en) * | 2020-08-18 | 2022-02-24 | 厦门网宿有限公司 | Cookie management method, intermediate node, and webvpn system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104159275B (en) | Method for connecting network and device | |
| EP3070659A1 (en) | Method, device and terminal for displaying application messages | |
| EP3561691A1 (en) | Method and apparatus for displaying webpage content | |
| CN105847430A (en) | Hybrid application page data access method and device | |
| CN106126632A (en) | Recommend method and device | |
| CN105068976A (en) | Ticket information exhibition method and device | |
| CN105677392A (en) | Method and apparatus for recommending applications | |
| CN105808731A (en) | Data storage method and device | |
| EP2924627A1 (en) | Method, device and system for event reminding | |
| CN107230137A (en) | Merchandise news acquisition methods and device | |
| CN105608064A (en) | Character replacement method and apparatus | |
| CN105739834A (en) | Menu displaying method and device | |
| CN106228374A (en) | Queuing service method and apparatus | |
| CN105678266A (en) | Method and device for combining photo albums of human faces | |
| CN105487758A (en) | Method and device for popup control of application software, and terminal equipment | |
| CN105843503A (en) | Application starting method and device as well as terminal equipment | |
| CN105100061A (en) | Method and device for detecting hijacking of website | |
| CN105976230A (en) | Processing method and apparatus for shopping request | |
| US11099916B2 (en) | Method and device for presenting information on terminal | |
| CN106130873A (en) | Information processing method and device | |
| CN105550213A (en) | Picture browsing method and device | |
| CN104836721A (en) | Group session message reminding method and group session message reminding device | |
| CN105808767A (en) | Data updating method and apparatus | |
| CN105630948A (en) | Web page display method and apparatus | |
| KR20180081640A (en) | Method and device for pushing user information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160727 |
|
| RJ01 | Rejection of invention patent application after publication |