CN104468318B - The method and server of inverse relationship chain are recycled in network communication - Google Patents
The method and server of inverse relationship chain are recycled in network communication Download PDFInfo
- Publication number
- CN104468318B CN104468318B CN201310429675.3A CN201310429675A CN104468318B CN 104468318 B CN104468318 B CN 104468318B CN 201310429675 A CN201310429675 A CN 201310429675A CN 104468318 B CN104468318 B CN 104468318B
- Authority
- CN
- China
- Prior art keywords
- recycling
- buddy list
- positive
- module
- library
- 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 invention discloses methods and server that inverse relationship chain is recycled in network communication, wherein this method comprises: receiving the buddy list read requests comprising Subscriber Number；The buddy list about Subscriber Number is read in good friend's database, number in buddy list is compared with the positive recycling number in the positive recycling library of storage, whether judge in buddy list comprising positive recycling number, if it is, the positive recycling number for including, the buddy list after being deleted then are deleted from buddy list；With the buddy list for the correspondence Subscriber Number that the buddy list after deletion updates storage.The present invention program can be realized the recycling to inverse relationship chain, and can reduce workload, improve recovery efficiency.
Description
Technical field
The present invention relates to methods and service that inverse relationship chain is recycled in network communication technology more particularly to network communication
Device.
Background technique
In network communications, normally, the user data about each Subscriber Number is stored in network side server.Lower mask
Body is illustrated with microblogging communication, and for Subscriber Number A, server is stored with the user data about Subscriber Number A, the user
Data include the buddy list formed by good friend's number of corresponding Subscriber Number A.
It is the instances of user data about each Subscriber Number of server storage in prior art network communication referring to Fig. 1,
Especially marked in figure about Subscriber Number A(UniA) and Subscriber Number B(UniB) buddy list, wherein about Subscriber Number
The buddy list of B includes Subscriber Number 1(Uni1), Subscriber Number 2(Uni2) ....Fig. 1 show the forward direction of each Subscriber Number
Relation chain, positive relationship chain are one kind of relation chain, it is generally the case that are with relation chain caused by user's active behavior, forward direction
Relation chain is generally shorter, such as microblogging listens to chain.
With popularizing for Internet service, the buddy list of the growth of amount of user data and each Subscriber Number is increasingly
Long, the capacity that server is used to store positive relationship chain is also increasing.It is multiple in order to reduce carrying cost and simplify system design
Polygamy in relation chain storage scheme, usually only stores unilateral relation chain, i.e. positive relationship chain, without storing inverse relationship chain.
Inverse relationship chain is the relation chain generated based on the passive behavior of user.Assuming that in the positive relationship chain of Subscriber Number M
Comprising Subscriber Number A, then the chaining key between Subscriber Number M is just inverse relationship chain for Subscriber Number A；Instead
It is usually long to relation chain, such as microblogging listened to chain.
It is equally illustrated with microblogging communication, micro- circle relation chain, only storage is using Subscriber Number A as the circle member of keyword
List does not store and (does not store Subscriber Number A in which good friend's circle by the reversed user data of keyword of Subscriber Number A
In, that is, inverse relationship chain is not stored).
In this way, recycling corresponding buddy list when needing to carry out Subscriber Number recycling according to Subscriber Number, can be realized
The recycling of positive relationship chain.For inverse relationship chain, the mode that traversal queries can be used is recycled, specifically: for user
Number A, after recycling its positive relationship chain；All buddy lists are traversed in user data, judge that each buddy list is one by one
No includes Subscriber Number A, if comprising releasing corresponding friend relation.Since user data includes that data volume is larger, traversal
Once need long time；Inverse relationship chain is recycled using traversal mode, heavy workload spends the time long, recovery efficiency
It is low.Therefore, the recycling in practical application and without reverse link, and only recycle forward link.
To sum up, when carrying out the recycling of relation chain number, how to realize the recycling of inverse relationship chain, become urgently to be resolved and ask
Topic.
Summary of the invention
The present invention provides a kind of method for recycling inverse relationship chain in network communication, this method be can be realized to reverse strand
The recycling on road, and can reduce workload, improve recovery efficiency.
The present invention provides the server for recycling inverse relationship chain in a kind of network communication, which be can be realized to anti-
Recycling to link, and can reduce workload, improve recovery efficiency.
A kind of method that inverse relationship chain is recycled in network communication, this method comprises:
Receive the buddy list read requests comprising Subscriber Number；
The buddy list about Subscriber Number is read in good friend's database, by the number in buddy list and is stored just
Whether the positive recycling number into recycling library is compared, judge comprising positive recycling number in buddy list, if it is,
The positive recycling number for including, the buddy list after being deleted are deleted from buddy list；
With the buddy list for the correspondence Subscriber Number that the buddy list after deletion updates storage.
Preferably, before the reception is comprising the buddy list read requests of Subscriber Number, this method further include:
Receive the positive recycling request comprising positive recycling number；
Forward direction recycling number is added in positive recycling library；
It deletes in good friend's database and about the positive buddy list for recycling number.
Preferably, when the buddy list deleted in good friend's database about positive recycling number, this method further include:
Positive recycling number is inquired from herd number library；
The positive recycling number inquired is deleted from herd number library.
Preferably, before the buddy list for the correspondence Subscriber Number that the buddy list with after deletion updates storage, it should
Method further include:
Judge in herd number library whether to include positive recycling number, if it is not, then executing described with good after deletion
The step of buddy list of the correspondence Subscriber Number of friendly list update storage.
Preferably, it is described in good friend's database read about the buddy list of Subscriber Number after, this method further include:
The buddy list read is fed back to requesting party；Alternatively,
After the buddy list for the correspondence Subscriber Number that the buddy list with after deletion updates storage, this method is also wrapped
It includes: feeding back updated buddy list to requesting party.
The server of inverse relationship chain is recycled in a kind of network communication, which includes data module and recycling module；
The data module receives the buddy list read requests comprising Subscriber Number；It reads and closes in good friend's database
In the buddy list of Subscriber Number, buddy list is sent to the recycling module；Receive the deletion of the recycling module feedback
Buddy list afterwards, with the buddy list for the correspondence Subscriber Number that received buddy list updates storage；
The recycling module, receive the buddy list from the data module, by buddy list number and storage
Positive recycling library in positive recycling number be compared, judge whether comprising positive recycling number in buddy list, if
It is that the positive recycling number for including then is deleted from buddy list, the buddy list after being deleted feeds back to the data mould
Block.
Preferably, the server further includes collection centre, the positive recycling request comprising positive recycling number is received, is sent
To the recycling module；
The recycling module receives the positive recycling request from the collection centre, forward direction recycling number is added to
In forward direction recycling library；And forward direction recycling request is sent to the data module；
The data module receives the positive recycling request from the recycling module, delete in good friend's database about
The buddy list of forward direction recycling number.
Preferably, the server further includes account module；
Forward direction recycling request is also sent to the account module by the recycling module；
The account module, the number logged in for storing registration；The positive recycling from the recycling module is received to ask
It asks, the positive recycling number that positive recycling request includes, the positive recycling number that will be inquired is inquired from herd number library
It is deleted from herd number library.
Preferably, the recycling module will also be looked into before the buddy list after deleting is fed back to the data module
It askes request and is sent to the account module, the inquiry request includes the positive recycling number deleted from buddy list；Receive institute
After the confirmation response for stating account module feedback, the buddy list after deletion is just fed back into the data module；
The account module receives the inquiry request from the recycling module, judge in herd number library whether include
Forward direction recycling number, if it is not, then being responded to the recycling module feedback acknowledgment.
Preferably, the data module, after reading in good friend's database about the buddy list of Subscriber Number, to asking
The buddy list that the side's of asking feedback is read；Alternatively, in the good friend of the correspondence Subscriber Number updated storage with the buddy list after deletion
After list, updated buddy list is fed back to requesting party.
From above scheme as can be seen that in the present invention, the buddy list read requests comprising Subscriber Number are received；In good friend
The buddy list about Subscriber Number is read in database, and the forward direction of number and storage in buddy list is recycled in library just
It is compared, is judged whether comprising positive recycling number in buddy list, if it is, being deleted from buddy list to recycling number
Except comprising positive recycling number, buddy list after being deleted；With the buddy list after deletion update storage to application
The buddy list of family number.In this way, when carrying out buddy list reading, by number of forward direction recycling in the buddy list of reading
Code is deleted, and to update buddy list, in turn, realizes the recycling to inverse relationship chain；Also, this mode is without storing magnanimity
Inverse relationship chain, reduce workload, improve recovery efficiency.
Detailed description of the invention
Fig. 1 is in the prior art in the user data schematic diagram example of server storage；
The method schematic flow chart of inverse relationship chain is recycled in the communication of Fig. 2 inventive network；
Fig. 3 is the method flow diagram example that inverse relationship chain is recycled in inventive network communication；
Fig. 4 is the server architecture schematic diagram that inverse relationship chain is recycled in inventive network communication.
Specific embodiment
To make the objectives, technical solutions, and advantages of the present invention clearer, below with reference to embodiment and attached drawing, to this
Invention is further described.
The present invention deletes the number of forward direction recycling in the buddy list of reading when carrying out buddy list reading,
To update buddy list, in turn, the recycling to inverse relationship chain is realized.Referring to fig. 2, anti-for recycling in inventive network communication
To the method schematic flow chart of relation chain comprising following steps:
Step 201, the buddy list read requests comprising Subscriber Number are received.
After user's logging on communication client, requesting party can send buddy list read requests to server, to obtain
Information about buddy list.
Step 202, buddy list about Subscriber Number is read in good friend's database, by buddy list number with
Whether the positive recycling number in the positive recycling library of storage is compared, judge in buddy list to include positive recycling number,
If it is, deleting the positive recycling number for including, the buddy list after being deleted from buddy list.
In server side, buddy list of good friend's database purchase about each number.Forward direction recycling library storage is positive
The number of recycling, specifically: after user's logging on communication client, if desired recycling the number used, then trigger positive relationship
Chain recycling sends the positive recycling request comprising positive recycling number to server；Server is received comprising positive recycling number
Positive recycling request；Forward direction recycling number is added in positive recycling library；Good friend is deleted to recycle according in library with about forward direction
The buddy list of number.
When user registers, the number to succeed in registration can be added in herd number library；In order to save herd number library
Space, in the above process, when buddy list in deleting good friend's database about positive recycling number, this method is also wrapped
It includes: inquiring positive recycling number from herd number library；The positive recycling number inquired is deleted.
Step 203, the buddy list of the correspondence Subscriber Number updated storage with the buddy list after deletion.
In practical applications, the number of positive recycling is possible to be reused by subsequent, distributes to the user of newest registration；
Correspondingly, the number will be added in herd number library；In this way, the positive recycling number that step 202 is deleted from buddy list can
It can be reused, and be added in herd number library by subsequent, in this case, if updated with the buddy list after deleting
The buddy list of the correspondence Subscriber Number of storage, will be present faulty operation, has an impact to register flow path；Therefore, in order into one
Whether step improves operation accuracy rate, before executing step 203, this method further include: judge in herd number library comprising corresponding
Positive recycling number, if it is not, then executing step 203；If shown accordingly just comprising corresponding positive recycling number
It is reused to recycling number, in order to avoid being mistakenly updated to buddy list, does not then execute step 203.
The present invention triggers the recycling of inverse relationship chain when carrying out buddy list reading, feeds back buddy list to requesting party
Opportunity, there are many implementations.For example, reading is fed back to requesting party after the buddy list about Subscriber Number can be read
Buddy list, the buddy list that this mode is fed back is preceding for it to carry out the updated list of inverse relationship link；It is carried out because current
Buddy list is read and the update of triggering, will be as the information for feeding back to requesting party when reading next time.For another example, it is also possible that with
After the buddy list for the correspondence Subscriber Number that buddy list after deletion updates storage, updated good friend's column are fed back to requesting party
Table；In this way, the update of inverse relationship chain is first carried out, current updated buddy list is fed back into requesting party, is fed back
To requesting party buddy list much sooner.
When carrying out buddy list reading, triggering recycling, by the number of positive recycling is deleted in the buddy list of reading
It removes, to update buddy list, in turn, realizes the recycling to inverse relationship chain；Also, this mode is when buddy list is read
Triggering recycling is recycled without storing the inverse relationship chain of magnanimity without by the way of traversing all buddy lists, from
And workload is reduced, improve recovery efficiency.
Below by Fig. 3, the method that inverse relationship chain is recycled in inventive network communication is illustrated comprising
Following steps:
Step 301, the positive recycling request comprising positive recycling number is received.
After user's logging on communication client, the number used is if desired recycled, then the recycling of positive relationship chain is triggered, to clothes
Business device sends the forward direction recycling request comprising positive recycling number.
Step 302, forward direction recycling number is added in positive recycling library.
Step 303, it deletes in good friend's database and about the positive buddy list for recycling number.
Step 304, positive recycling number is inquired from herd number library, by the positive number that recycles inquired from registration
Number is deleted in library.
When user registers, the number to succeed in registration can be added in herd number library；In order to save herd number library
Space, in the above process, when buddy list in deleting good friend's database about positive recycling number, delete registration together
Positive recycling number in number library.
Step 305, the buddy list read requests comprising Subscriber Number are received.
When needed, request direction server sends buddy list read requests, to obtain the information about buddy list.
Step 306, buddy list about Subscriber Number is read in good friend's database, by buddy list number with
Whether the positive recycling number in the positive recycling library of storage is compared, judge in buddy list to include positive recycling number,
If it is, deleting the positive recycling number for including, the buddy list after being deleted from buddy list.
Step 307, judge whether comprising positive recycling number in herd number library, if it is not, then with good after deletion
The buddy list of the correspondence Subscriber Number of friendly list update storage.
Step 308, updated buddy list is fed back to requesting party.
In the present embodiment, current updated buddy list is sent to requesting party, makes the good friend's column for feeding back to requesting party
Table is much sooner.
Network communication of the present invention specifically for example microblogging communication, qq communication etc..
It referring to fig. 4, is the server architecture schematic diagram that inverse relationship chain is recycled in inventive network communication, the server packet
Including the server includes data module and recycling module；
The data module receives the buddy list read requests comprising Subscriber Number；It reads and closes in good friend's database
In the buddy list of Subscriber Number, buddy list is sent to the recycling module；Receive the deletion of the recycling module feedback
Buddy list afterwards, with the buddy list for the correspondence Subscriber Number that received buddy list updates storage；
The recycling module, receive the buddy list from the data module, by buddy list number and storage
Positive recycling library in positive recycling number be compared, judge whether comprising positive recycling number in buddy list, if
It is that the positive recycling number for including then is deleted from buddy list, the buddy list after being deleted feeds back to the data mould
Block.
Preferably, the server further includes collection centre, the positive recycling request comprising positive recycling number is received, is sent
To the recycling module；
The recycling module receives the positive recycling request from the collection centre, forward direction recycling number is added to
In forward direction recycling library；And forward direction recycling request is sent to the data module；
The data module receives the positive recycling request from the recycling module, delete in good friend's database about
The buddy list of forward direction recycling number.
Preferably, the server further includes account module；
Forward direction recycling request is also sent to the account module by the recycling module；
The account module, the number logged in for storing registration；The positive recycling from the recycling module is received to ask
It asks, the positive recycling number that positive recycling request includes, the positive recycling number that will be inquired is inquired from herd number library
It is deleted from herd number library.
Preferably, the recycling module will also be looked into before the buddy list after deleting is fed back to the data module
It askes request and is sent to the account module, the inquiry request includes the positive recycling number deleted from buddy list；Receive institute
After the confirmation response for stating account module feedback, the buddy list after deletion is just fed back into the data module；
The account module receives the inquiry request from the recycling module, judge in herd number library whether include
Forward direction recycling number, if it is not, then being responded to the recycling module feedback acknowledgment.
In this example, when requesting party reads user data, forwarding is a to arrive recycling module, and recycling module judges whether there is back
The good friend of receipts；If so, triggering recycling logic.Forward direction recycling library is stored in recycling module, receives buddy list reading and reads after asking,
It is first filtered in recycling module, then account module is gone to verify whether to recycle, the influence to account module is effectively reduced.
Preferably, the data module, after reading in good friend's database about the buddy list of Subscriber Number, to asking
The buddy list that the side's of asking feedback is read；Alternatively, in the good friend of the correspondence Subscriber Number updated storage with the buddy list after deletion
After list, updated buddy list is fed back to requesting party.
The foregoing is merely illustrative of the preferred embodiments of the present invention, is not intended to limit the invention, all in essence of the invention
Within mind and principle, any modification, equivalent substitution, improvement and etc. done be should be included within the scope of the present invention.
Claims (10)
1. recycling the method for inverse relationship chain in a kind of network communication, which is characterized in that this method comprises:
Receive the buddy list read requests comprising Subscriber Number；
The buddy list about Subscriber Number is read in good friend's database, and the forward direction of number and storage in buddy list is returned
Whether the positive recycling number received in library is compared, judge comprising positive recycling number in buddy list, if it is, from good
The positive recycling number for including, the buddy list after being deleted are deleted in friendly list；
With the buddy list for the correspondence Subscriber Number that the buddy list after deletion updates storage.
2. the method as described in claim 1, which is characterized in that described to receive the buddy list read requests comprising Subscriber Number
Before, this method further include:
Receive the positive recycling request comprising positive recycling number；
Forward direction recycling number is added in positive recycling library；
It deletes in good friend's database and about the positive buddy list for recycling number.
3. method according to claim 2, which is characterized in that described to delete in good friend's database about positive recycling number
When buddy list, this method further include:
Positive recycling number is inquired from herd number library；
The positive recycling number inquired is deleted from herd number library.
4. the method as described in claim 1, which is characterized in that it is described with delete after buddy list update storage to application
Before the buddy list of family number, this method further include:
Judge whether comprising positive recycling number in herd number library, if it is not, then executing the good friend's column used after deleting
The step of buddy list for the correspondence Subscriber Number that table updates storage.
5. method according to any one of claims 1 to 4, which is characterized in that it is described in good friend's database read about
After the buddy list of Subscriber Number, this method further include: the buddy list read is fed back to requesting party；Alternatively,
After the buddy list for the correspondence Subscriber Number that the buddy list with after deletion updates storage, this method further include: to
Requesting party feeds back updated buddy list.
6. in a kind of network communication recycle inverse relationship chain server, which is characterized in that the server include data module and
Recycling module；
The data module receives the buddy list read requests comprising Subscriber Number；In good friend's database read about with
Buddy list is sent to the recycling module by the buddy list of family number；After the deletion for receiving the recycling module feedback
Buddy list, with the buddy list for the correspondence Subscriber Number that received buddy list updates storage；
The recycling module receives the buddy list from the data module, by the number in buddy list and stores just
Whether the positive recycling number into recycling library is compared, judge comprising positive recycling number in buddy list, if it is,
The positive recycling number for including is deleted from buddy list, the buddy list after being deleted feeds back to the data module.
7. server as claimed in claim 6, which is characterized in that the server further includes collection centre, is received comprising forward direction
The positive recycling request for recycling number, is sent to the recycling module；
The recycling module, receives the positive recycling request from the collection centre, and forward direction recycling number is added to forward direction
It recycles in library；And forward direction recycling request is sent to the data module；
The data module receives the positive recycling request from the recycling module, deletes in good friend's database about forward direction
Recycle the buddy list of number.
8. server as claimed in claim 7, which is characterized in that the server further includes account module；
Forward direction recycling request is also sent to the account module by the recycling module；
The account module, the number logged in for storing registration；The positive recycling request from the recycling module is received, from
The positive positive recycling number for recycling request and including is inquired in herd number library, by the positive number that recycles inquired from registration
Number is deleted in library.
9. server as claimed in claim 8, which is characterized in that the recycling module, the buddy list after it will delete are anti-
Before the data module of feeding, inquiry request is also sent to the account module, the inquiry request includes to arrange from good friend
The positive recycling number that table is deleted；It is just that the buddy list after deletion is anti-after the confirmation response for receiving the account module feedback
It feeds the data module；
Whether the account module receives the inquiry request from the recycling module, judge in herd number library comprising forward direction
Number is recycled, if it is not, then responding to the recycling module feedback acknowledgment.
10. the server as described in any one of claim 6 to 9, which is characterized in that the data module, in good friend's data
After reading in library about the buddy list of Subscriber Number, the buddy list read is fed back to requesting party；Alternatively, after with deletion
The buddy list of correspondence Subscriber Number that updates storage of buddy list after, feed back updated buddy list to requesting party.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310429675.3A CN104468318B (en) | 2013-09-18 | 2013-09-18 | The method and server of inverse relationship chain are recycled in network communication |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201310429675.3A CN104468318B (en) | 2013-09-18 | 2013-09-18 | The method and server of inverse relationship chain are recycled in network communication |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN104468318A CN104468318A (en) | 2015-03-25 |
| CN104468318B true CN104468318B (en) | 2019-03-26 |
Family
ID=52913723
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201310429675.3A Active CN104468318B (en) | 2013-09-18 | 2013-09-18 | The method and server of inverse relationship chain are recycled in network communication |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN104468318B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106470150B (en) * | 2015-08-21 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Relation chain storage method and device |
| CN106534234B (en) * | 2015-09-09 | 2020-04-28 | 腾讯科技（深圳）有限公司 | Relationship chain processing system, method and device |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6154764A (en) * | 1997-01-31 | 2000-11-28 | Fujitsu Limited | On-line forum-type electronic conference system maintaining consistency of messages |
| CN101252621A (en) * | 2008-04-10 | 2008-08-27 | 中兴通讯股份有限公司 | Call list managing method and system |
| CN102056106A (en) * | 2009-10-29 | 2011-05-11 | 腾讯数码（天津）有限公司 | Method and system for updating address lists in real time |
| CN102088519A (en) * | 2009-12-08 | 2011-06-08 | 中国移动通信集团公司 | Address book management method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7080122B2 (en) * | 2000-08-07 | 2006-07-18 | Return Path, Inc. | System and process for updating electronic messaging accounts |
-
2013
- 2013-09-18 CN CN201310429675.3A patent/CN104468318B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6154764A (en) * | 1997-01-31 | 2000-11-28 | Fujitsu Limited | On-line forum-type electronic conference system maintaining consistency of messages |
| CN101252621A (en) * | 2008-04-10 | 2008-08-27 | 中兴通讯股份有限公司 | Call list managing method and system |
| CN102056106A (en) * | 2009-10-29 | 2011-05-11 | 腾讯数码（天津）有限公司 | Method and system for updating address lists in real time |
| CN102088519A (en) * | 2009-12-08 | 2011-06-08 | 中国移动通信集团公司 | Address book management method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN104468318A (en) | 2015-03-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110609844B (en) | Data updating method, device and system | |
| CN106612301B (en) | The method for pushing and device of more new data | |
| EP2833581B1 (en) | Method and device for supporting content subscription in content network | |
| US20090092131A1 (en) | Method and Device for Rejecting Redundantly Retransmitted SIP Messages | |
| CN106339267B (en) | A kind of Object Query method and server-side | |
| CN110519240B (en) | Single sign-on method, device and system | |
| CN103051717A (en) | Method, device and equipment for processing http request | |
| US20110060800A1 (en) | Method of guaranteeing the deliverability of emails and other messages | |
| CN105491078B (en) | Data processing method and device, SOA system in SOA system | |
| CN102065136A (en) | P2P (Peer-to-Peer) network safety data transmission method and system | |
| US20170318521A1 (en) | Method for realizing resource attribute notification, and common service entity | |
| CN104468318B (en) | The method and server of inverse relationship chain are recycled in network communication | |
| CN110474963A (en) | A kind of resource access method based on zookeeper, system, medium and electronic equipment | |
| EP2224381A1 (en) | Method and apparatus for case-based service composition | |
| US10025859B2 (en) | Method and system for second-degree friend query | |
| CN109063140A (en) | A kind of data query method, transfer server and computer readable storage medium | |
| CN102594787B (en) | Data grab method, system and routing server | |
| CN108241685A (en) | The method and inquiring client terminal of data query | |
| CN101753561A (en) | Business cluster processing method and cluster system | |
| CN101741889B (en) | Method, system and service for centralized management of network services | |
| CN109818948A (en) | Using dispositions method, device, system, equipment and medium | |
| JP2006146615A (en) | Object-related information management program, management method and management apparatus | |
| CN113992664B (en) | Cluster communication method, related device and storage medium | |
| CN113791733A (en) | Information storage method, device, equipment and storage medium | |
| KR101674294B1 (en) | Apparatus for operating data structure capable of random access and state access and operating method thereof |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |