CN102025728A - Scheduling method under client-side/server-side architecture and server - Google Patents
Scheduling method under client-side/server-side architecture and server Download PDFInfo
- Publication number
- CN102025728A CN102025728A CN2010105634984A CN201010563498A CN102025728A CN 102025728 A CN102025728 A CN 102025728A CN 2010105634984 A CN2010105634984 A CN 2010105634984A CN 201010563498 A CN201010563498 A CN 201010563498A CN 102025728 A CN102025728 A CN 102025728A
- Authority
- CN
- China
- Prior art keywords
- lock state
- interface
- service end
- single example
- client
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
Abstract
The invention discloses a scheduling method under a client-side/server-side architecture and a server. The method comprises: a server side receives a request message for requesting a single case from a client side; the server side judges whether the interface of the single case requested by the client side is being visited, or whether the single case requested by the client side is being operated; and if so, the server side transmits a response message for rejecting the access of the client side to the client side. According to the invention, the problem of data chaos caused by failure of mutual exclusion in the prior art is solved.
Description
Technical field
The present invention relates to the communications field, dispatching method (Double Level Lock Schedule Method, DL under a kind of C/S (Client/Server, client/service end) framework
2SM) and server.
Background technology
Under the C/S framework, same service end need be supported a plurality of clients simultaneously, the access services end that a plurality of clients can be concurrent.For some function that service end provided, a plurality of users of synchronization can use simultaneously by a plurality of clients.But, some functions are arranged, between the client being " mutual exclusion ", promptly do not allow a plurality of clients to use simultaneously at synchronization.In user oriented application program, the function that some application program provided has its particularity to a certain extent, its special requirement is also arranged under abnormal conditions, therefore, use traditional multithreading mutual exclusion dispatching method often to be difficult to satisfy the mutual exclusion requirement of the concurrent access services end of multi-client under the C/S framework.
In OMC (Operation Management Center, operation maintenance center), need the function of mutual exclusion can be divided into two types, the first, other mutual exclusion of NE-level is promptly for same network element, a client can only be arranged in operation at synchronization, preserve as the modification of configuration parameter; Second, the mutual exclusion of functional class, promptly no longer distinguish network element, but can only there be a client to use at synchronization for some functions, as configuration synchronization, require synchronization to be merely able to have a client to open this function interface of configuration synchronization, usually this function with mutual exclusion of functional class is called " single example " function, promptly this function can only have an example being used.
For other mutual exclusion of NE-level, can use mutually exclusive privilege to guarantee, still,, therefore can not use existing mutually exclusive privilege to guarantee because mutually exclusive privilege is not need to depend on network element for the mutual exclusion of functional class.The mutual exclusion that needs a kind of new method of use to come assurance function to use.
For the mutual exclusion on the function, method in the past is to use a kind of method of function lock: be mutual exclusion lock attribute of each single example function setting in service end, when certain client attempts entering the function menu of single example, go service end to judge whether this function is locked, if locked, represent that other clients take, this client can't enter this function menu so; If do not locked, pin this function to the service end application so, do not allow other clients to use simultaneously, open this function menu afterwards, when user's complete operation, during the closing function page,, allow other clients to use to service end notice release function lock.
Because function lock used herein has guaranteed that synchronization can only have a client to open single example function operations interface, be that other single example of operation interface level guarantees, therefore it is called the function lock of GUI Level (interface rank) here, locks scheduling model such as Fig. 1 by the substance that GUI Level function lock is realized.
Use the function lock of this GUI Level, look success solution problem, but think over, also have certain situation not consider.
The function lock of present existing GUI Level, under normal circumstances can run well, but, when certain client that has got access to the function lock withdraws from unusually, such as suspension, outage, force the end process, the function lock that client can initiatively not gone to require service end to discharge and oneself taken this time, at this moment lock still at seizure condition in the function of service, if other clients attempt using this function, can can't enter function interface because obtain less than the function lock, but the function that has not in fact had other clients to take this function has been locked, and withdraws from because take the client of this function lock.
And function lock can be released even client withdraws from the back unusually, also can there are the following problems:
After client uses single example function to initiate to carry out request, request service end also do not have complete in, client withdraws from unusually, serviced end listens to, so discharged the function lock that this client takies.Though there is not this time client to take this function, the request of this function is still carried out in service end, should be the function of single example, also can go wrong if therefore have other clients to use this constantly at this.For example, customer end A is initiated in batches, and parameter derives, derived process need 10 minutes, customer end A is entering when deriving the interface to the service end application parameter export function lock in batches, if the derivation process is when service end is carried out the 5th minute, the client outage is withdrawed from unusually, the state detector of service end has listened to withdrawing from of client, discharge the batch parameter export function lock that customer end A takies, allow other clients to use parameter export function in batches, this time, problem occurred, because this moment, the parameter derivation was also carried out in service end in batches, do not withdraw from the back unusually with regard to real end, if this moment, other clients re-used this function in client, will with the different design of single example function, problems such as data corruption appear.
Summary of the invention
Main purpose of the present invention is to provide dispatching method and the server under a kind of C/S framework, has solved in the prior art owing to can not mutual exclusion causing occurring the data corruption problem.
According to an aspect of the present invention, provide the dispatching method under a kind of client/service end framework, comprised the steps: that service end receives the request message that client is used to ask single example; Service end judges whether the single example whether is just asking in accessed or client at the interface of single example that client is asked is moved; Just moved at single example that accessed or client are asked if judge the interface of single example that client asks, then service end sends to client and is used to refuse the response message that client inserts.
Further, service end judges that the step whether single example that whether is just asking in accessed or client at the interface of single example that client is asked is being moved comprises: service end judges whether interface rank function lock state is in the lock state, perhaps, whether rank function lock state is in the lock state during operation; If interface rank function lock state is in the lock state, then service end judge single example the interface just accessed, perhaps, if rank function lock state is in the lock state during operation, then service end judges that single example is moved.
Further, do not have accessed and single example not moved if judge the interface of single example, also comprise: service end allows client access service end; Rank function lock state is set to lock-out state when service end interface rank function lock state and operation.
Further, after rank function lock state is set to lock-out state when service end interface rank function lock state and operation, also comprise: when the interface of single example is withdrawed from unusually, service end interface rank function lock state is set to not lock state, and rank function lock state is set to lock-out state when moving.
Further, after rank function lock state is set to lock-out state when service end interface rank function lock state and operation, also comprise: when single example of service end operation withdraws from unusually, service end interface rank function lock state is set to lock-out state, and rank function lock state is set to not lock state when moving.
Further, after rank function lock state was set to lock-out state when service end interface rank function lock state and operation, also comprise: when the interface of single example was normally withdrawed from, service end interface rank function lock state was set to not lock state; Judge that whether service end is also at the single example of operation, if rank function lock state was set to lock-out state when then service end was moved; Otherwise rank function lock state is set to not lock state when moving.
Further, after rank function lock state is set to lock-out state when service end interface rank function lock state and operation, also comprise: when single example of service end operation normally withdrawed from, rank function lock state was set to not lock state when service end was moved; Whether judge client also at the interface of the single example of visit, if then service end interface rank function lock state is set to lock-out state, otherwise interface rank function lock state is set to not lock state.
According to another aspect of the present invention, provide a kind of server, having comprised: receiving element is used to receive the request message that client is used to ask single example; Judging unit, whether the single example whether is just asking in accessed or client at the interface of the single example that is used to judge that client is asked is moved; Transmitting element when being used for single example of just asking in accessed or client when interface that judgment unit judges goes out single example that client asks by operation, sending and is used to refuse the response message that client inserts.
Further, judging unit comprises: first judge module is used to judge whether interface rank function lock state is in the lock state, if interface rank function lock state is in the lock state, the interface of then representing single example is just accessed; Second judge module, whether rank function lock state is in the lock state when being used for judging operation, and rank function lock state is in the lock state during as if operation, represents that then single example is moved.
Further, above-mentioned server also comprises: access unit when being used for not having accessed and single example by operation at the interface that judgment unit judges goes out single example, allows the client access server; The unit is set, is used for after the client access server, rank function lock state is set to lock-out state when interface rank function lock state and operation.
Further, the unit is set comprises: first is provided with module, and when being used for normally or unusually withdrawing from the interface of single example, interface rank function lock state is set to not lock state; Second is provided with module, is used for when single example of service end operation normally or unusually withdraws from, and rank function lock state is set to not lock state when moving.
In the present invention, judge by service end whether the single example whether is just asking in accessed or client at the interface of single example that client is asked is moved, make that single example can only be simultaneously performed by a client, thereby solved in the prior art owing to can not mutual exclusion causing occurring the data corruption problem mutual exclusion scheduling when reasonably having realized the concurrent visit of multi-client under the C/S framework.In addition,, make under abnormal conditions, also to have guaranteed the mutual exclusion state accurately, improved ease for use, correctness and the robustness of mutual exclusion scheduling by the scheduling of two-bolt lock.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the substance lock scheduling model of prior art GUI Level function lock;
Fig. 2 is a kind of preferred flow charts that provides according to the dispatching method under embodiment of the invention client/service end framework;
Fig. 3 is a kind of preferred structure block diagram that server provides according to the present invention;
Fig. 4 substance lock scheduling model of client state detector (Client Status Detector) that has been the adding that provides according to the dispatching method under embodiment of the invention client/service end framework;
Fig. 5 is the scheduling model DL2SM that provides according to the dispatching method under embodiment of the invention client/service end framework;
Fig. 6 is the client executing flow chart of the another kind of embodiment that provides according to the dispatching method under embodiment of the invention client/service end framework;
Fig. 7 is that the service end of the another kind of embodiment that provides according to the dispatching method under embodiment of the invention client/service end framework is received the execution flow process of obtaining after the GUI Level Lock request;
Fig. 8 is the function lock state exchange flow chart of the Running Level (rank during operation) of the another kind of embodiment that provides according to the dispatching method under embodiment of the invention client/service end framework.
Embodiment
Hereinafter will describe the present invention with reference to the accompanying drawings and in conjunction with the embodiments in detail.Need to prove that under the situation of not conflicting, embodiment and the feature among the embodiment among the application can make up mutually.
Embodiment 1
Referring to Fig. 2, comprise the steps: according to the dispatching method under the client/service end framework of this preferred embodiment
S202, service end receives the request message that client is used to ask single example;
S204, service end judges whether the single example whether is just asking in accessed or client at the interface of single example that client is asked is moved;
S206 is just moved at single example that accessed or client are asked if judge the interface of single example that client asks, and then service end sends to client and is used to refuse the response message that client inserts.
In this preferred embodiment, judge by service end whether the single example whether is just asking in accessed or client at the interface of single example that client is asked is moved, make that single example can only be simultaneously performed by a client, thereby solved in the prior art owing to can not mutual exclusion causing occurring problems such as data corruption the mutual exclusion scheduling when reasonably having realized the concurrent visit of multi-client under the C/S framework.
Preferably, service end judges that the step whether single example that whether is just asking in accessed or client at the interface of single example that client is asked is being moved comprises: service end judges whether interface rank function lock state is in the lock state, perhaps, whether rank function lock state is in the lock state during operation; If interface rank function lock state is in the lock state, then service end judge single example the interface just accessed, perhaps, if rank function lock state is in the lock state during operation, then institute's service end judges that single example is moved.In this preferred embodiment, when rank function lock is in the lock state when guaranteeing interface rank function lock or operation, be that the accessed or single example in interface of single example is when being moved, single example can only be simultaneously performed by a client, thereby guaranteed the mutual exclusion state, further improved ease for use, correctness and the robustness of mutual exclusion scheduling.
Preferably, do not have accessed and single example not moved if judge the interface of single example, also comprise: service end allows client access service end; Rank function lock state is set to lock-out state when service end interface rank function lock state and operation.In this preferred embodiment, when having guaranteed not have at the interface of single example accessed and single example by operation, client can the access service end, has further guaranteed the mutual exclusion state, has improved ease for use, correctness and the robustness of mutual exclusion scheduling.
Preferably, after rank function lock state is set to lock-out state when service end interface rank function lock state and operation, also comprise: when the interface of single example is withdrawed from unusually, service end interface rank function lock state is set to not lock state, and rank function lock state is set to lock-out state when moving.In this preferred embodiment, the mutual exclusion state the when interface that has guaranteed single example is withdrawed from has unusually guaranteed that further data passes is accurate, has improved correctness.
Preferably, after rank function lock state is set to lock-out state when service end interface rank function lock state and operation, also comprise: when single example of service end operation withdraws from unusually, service end interface rank function lock state is set to lock-out state, and rank function lock state is set to not lock state when moving.In this preferred embodiment, the mutual exclusion state when the single example that has guaranteed the service end operation withdraws from has unusually guaranteed further that data passes is accurate, has improved correctness.
Preferably, after rank function lock state was set to lock-out state when service end interface rank function lock state and operation, also comprise: when the interface of single example was normally withdrawed from, service end interface rank function lock state was set to not lock state; Judge that whether service end is also at the single example of operation, if rank function lock state was set to lock-out state when then service end was moved; Otherwise rank function lock state is set to not lock state when moving.In this preferred embodiment, the mutual exclusion state the when interface that has guaranteed single example is normally withdrawed from has guaranteed that further data passes is accurate, has improved correctness.
Preferably, after rank function lock state is set to lock-out state when service end interface rank function lock state and operation, also comprise: when single example of service end operation normally withdrawed from, rank function lock state was set to not lock state when service end was moved; Whether judge client also at the interface of the single example of visit, if then service end interface rank function lock state is set to lock-out state, otherwise interface rank function lock state is set to not lock state.In this preferred embodiment, the mutual exclusion state when the single example that has guaranteed the service end operation normally withdraws from has guaranteed further that data passes is accurate, has improved correctness.
Embodiment 2
Referring to Fig. 3, the invention provides a kind of server that adopts the dispatching method under client/service end framework, comprising: receiving element 301 is used to receive the request message that client is used to ask single example; Judging unit 302, whether the single example whether is just asking in accessed or client at the interface of the single example that is used to judge that client is asked is moved; Transmitting element 303 when being used for single example of just asking in accessed or client when interface that judgment unit judges goes out single example that client asks by operation, sending and is used to refuse the response message that client inserts.
In this preferred embodiment, judge by service end whether the single example whether is just asking in accessed or client at the interface of single example that client is asked is moved, make that single example can only be simultaneously performed by a client, thereby solved in the prior art owing to can not mutual exclusion causing occurring problems such as data corruption the mutual exclusion scheduling when reasonably having realized the concurrent visit of multi-client under the C/S framework.
Preferably, judging unit 302 comprises: first judge module 3021 is used to judge whether interface rank function lock state is in the lock state, if interface rank function lock state is in the lock state, the interface of then representing single example is just accessed; Second judge module 3022, whether rank function lock state is in the lock state when being used for judging operation, and rank function lock state is in the lock state during as if operation, represents that then single example is moved.In this preferred embodiment, when rank function lock is in the lock state when guaranteeing interface rank function lock or operation, be that the accessed or single example in interface of single example is when being moved, single example cannot be performed by a plurality of clients, thereby guaranteed the mutual exclusion state, further improved ease for use, correctness and the robustness of mutual exclusion scheduling.
Preferably, server also comprises: access unit 304 when being used for not having accessed and single example by operation at the interface that judging unit 302 is judged single example, allows the client access server; Unit 305 is set, is used for after the client access server, rank function lock state is set to lock-out state when interface rank function lock state and operation.In this preferred embodiment, rank function lock is in when not locking state when guaranteeing interface rank function lock and operation, be that the accessed and single example in the interface of single example is during by operation, single example can only be simultaneously performed by a client, thereby guaranteed the mutual exclusion state, further improved ease for use, correctness and the robustness of mutual exclusion scheduling.
Preferably, unit 305 is set comprises: first is provided with module 3051, and when being used for normally or unusually withdrawing from the interface of single example, interface rank function lock state is set to not lock state; Second is provided with module 3052, is used for when single example of service end operation normally or unusually withdraws from, and rank function lock state is set to not lock state when moving.In this preferred embodiment, the mutual exclusion state when the single example that has guaranteed the server operation normally or unusually withdraws from has guaranteed further that data passes is accurate, has improved correctness.
Thereby as can be seen, a kind of embodiment of the present invention's employing is the two-bolt lock mutual exclusion dispatching method of rank (Running Level) lock when using interface rank (GUI Level) lock and operation simultaneously.
Embodiment 3
Referring to Fig. 4, in the DL2SM dispatching method, at first, use a client state detector 402 (Client Status Detector) to monitor withdrawing from of client 403 in service end 401, specific implementation can be by the timing handshake mechanism.When service end 401 listens to that client 403 withdraws from unusually and not initiatively the release function lock time, can initiate to discharge all locks that the client 403 that withdraws from takies by service end 401.
Use this model that has client state detector 402, can prevent the entanglement of the service end 401 functional incompatibilities lock state that client 403 causes when outage, suspension unpredictable unusual occurring, guarantee the correctness and the robustness of function lock to a certain extent.
Referring to Fig. 5, then, be the function lock attribute that each single example function increases a Running Level (rank during operation) in service end 501, be used for representing whether single example function is just carried out in service end.Detect the state of client 503 simultaneously by client state detector 502, the function lock state of Running Level is safeguarded by service end 501, when single example function when service end 501 is carried out beginning, Running Level function lock state is changed to Locked (locking), when carrying out end, Running Level function lock state is changed to Unlocked (lock).
The function lock of GUI Level and the function lock of Running Level have constituted two-bolt lock jointly.
Embodiment 4
When the user when client attempt to be used single example function, earlier to the Mutex of service end Pool (set of mutual exclusion function lock) application GUI Level Lock (interface rank function lock), (service end is after receiving GUI Level Lock request, check the state of Running Level Lock (rank function lock during operation), return results in view of the above), if application failure, then do not allow the user to enter operation interface, if apply for successfully, the opening operation interface, and GUI Level Lock state is changed to Locked (locking).
The client executing flow process is referring to Fig. 6, and step is as follows:
S602, client is clicked single example function menu;
Does S604 to service end application GUI Level Lock, and judge whether application successful? if success then goes to step S606; If failure then goes to step S612;
S606 enters single example function interface;
S608 withdraws from after the executable operations;
S610, the notification service end discharges Lock, changes step S614;
S612, the single example function of prompting user is used by other clients, can't enter;
S614 finishes.
After service end was received client application GUI Level Lock request, returning the successful condition of application was that GUI Level Lock is not taken by other clients, and the state of the Running Level Lock of single example function is Unlocked.
The execution flow process of service end response application GUI Level Lock request is referring to Fig. 7, and step is as follows:
S702, service end is received the GUI Level Lock request of obtaining of client;
S704, whether the state of the pairing Running Level of GUI Level Lock Lock is Unlocked.If then go to step S706; Otherwise, go to step 712;
S706, whether the state of GUI Level Lock is Unlocked.If then go to S708; Otherwise, go to S712;
S708, GUI Level Lock state is changed to Locked;
S710 returns success, and changes step S714;
S712 returns failure;
S714 finishes.
The function of Running Level lock state safeguarded by service end, when single example function when service end is carried out beginning, Running Level function lock state is changed to Locked, when carrying out when finishing, Running Level function lock state is changed to Unlocked.
The function lock state exchange flow chart of Running Level is referring to Fig. 8, and step is as follows:
S802, service end begins fill order's example function;
S804, the state that Running Level Lock is set is Locked;
S806, the single example function executing of service end is finished;
S808, the state that Running Level Lock is set is Unlocked;
S810 finishes.
As can be seen from the above description, the present invention has realized following technique effect:
This method is used other mutual exclusion lock of interface level, guarantees to have only a client to obtain using the authority of mutual exclusion function under the normal condition; Occur under the unusual situation in client, rank was locked the correctness that guarantees mutually exclusive privilege when this method was used the operation of service end, if the i.e. mutual exclusion function of service end operation stops, then discharged the authority of client; If the mutual exclusion function of service end still in operation, is then refused other client application mutually exclusive privileges.Thereby guaranteed the correct scheduling of mutual exclusion system in any case.
Lock by double-deck function the concurrent access services end of a plurality of clients has been done effective control, mutual exclusion scheduling when not only reasonably having realized the concurrent visit of multi-client under the C/S framework, and under abnormal conditions, also guaranteed the mutual exclusion state accurately, improved ease for use, correctness and the robustness of mutual exclusion scheduling.
Obviously, those skilled in the art should be understood that, above-mentioned each module of the present invention or each step can realize with the general calculation device, they can concentrate on the single calculation element, perhaps be distributed on the network that a plurality of calculation element forms, alternatively, they can be realized with the executable program code of calculation element, thereby, they can be stored in the storage device and carry out by calculation element, and in some cases, can carry out step shown or that describe with the order that is different from herein, perhaps they are made into each integrated circuit modules respectively, perhaps a plurality of modules in them or step are made into the single integrated circuit module and realize.Like this, the present invention is not restricted to any specific hardware and software combination.
The above is the preferred embodiments of the present invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (11)
1. the dispatching method under client/service end framework is characterized in that, comprises the steps:
Service end receives the request message that client is used to ask single example;
Described service end judges whether the single example whether is just asking in accessed or described client at the interface of single example that described client is asked is moved;
Just moved at single example that accessed or described client are asked if judge the interface of single example that described client asks, then described service end sends to described client and is used to refuse the response message that described client inserts.
2. method according to claim 1 is characterized in that, described service end judges that the step whether single example that whether is just asking in accessed or described client at the interface of single example that described client is asked is being moved comprises:
Described service end judges whether interface rank function lock state is in the lock state, and perhaps, whether rank function lock state is in the lock state during operation;
If described interface rank function lock state is in the lock state, then described service end judges that the interface of described single example is just accessed, perhaps, if rank function lock state is in the lock state during described operation, then described service end judges that described single example is moved.
3. method according to claim 2 is characterized in that, does not have accessed and described single example not moved if judge the interface of described single example, also comprises:
Described service end allows described client to insert described service end;
Rank function lock state is set to lock-out state when the described interface of described service end rank function lock state and described operation.
4. method according to claim 3 is characterized in that, after rank function lock state is set to lock-out state when the described interface of described service end rank function lock state and described operation, also comprises:
When the interface of described single example was withdrawed from unusually, the described interface of described service end rank function lock state was set to not lock state, and rank function lock state is set to lock-out state during described operation.
5. method according to claim 3 is characterized in that, after rank function lock state is set to lock-out state when the described interface of described service end rank function lock state and described operation, also comprises:
When described single example of described service end operation withdrawed from unusually, the described interface of described service end rank function lock state was set to lock-out state, and rank function lock state is set to not lock state during described operation.
6. method according to claim 3 is characterized in that, after rank function lock state is set to lock-out state when the described interface of described service end rank function lock state and described operation, also comprises:
When the interface of described single example was normally withdrawed from, the described interface of described service end rank function lock state was set to not lock state;
Judge described service end whether also at the described single example of operation, if rank function lock state is set to lock-out state during the described operation of then described service end; Otherwise rank function lock state is set to not lock state during described operation.
7. method according to claim 3 is characterized in that, after rank function lock state is set to lock-out state when the described interface of described service end rank function lock state and described operation, also comprises:
When described single example of described service end operation normally withdrawed from, rank function lock state was set to not lock state during the described operation of described service end;
Whether judge described client also at the interface of the described single example of visit, if the described interface of then described service end rank function lock state is set to lock-out state, otherwise described interface rank function lock state is set to not lock state.
8. a server is characterized in that, comprising:
Receiving element is used to receive the request message that client is used to ask single example;
Judging unit, whether the single example whether is just asking in accessed or described client at the interface of the single example that is used to judge that described client is asked is moved;
Transmitting element when being used for single example of just asking in accessed or described client when interface that described judgment unit judges goes out single example that described client asks by operation, sending and is used to refuse the response message that described client inserts.
9. server according to claim 8 is characterized in that, described judging unit comprises:
First judge module is used to judge whether interface rank function lock state is in the lock state, if described interface rank function lock state is in the lock state, the interface of then representing described single example is just accessed;
Second judge module, whether rank function lock state is in the lock state when being used for judging operation, if rank function lock state is in the lock state during described operation, represents that then described single example is moved.
10. server according to claim 8 is characterized in that, also comprises:
Access unit when being used for not having accessed and described single example by operation at the interface that described judgment unit judges goes out described single example, allows described client to insert described server;
The unit is set, is used for after described client inserts described server, rank function lock state is set to lock-out state when described interface rank function lock state and described operation.
11. server according to claim 10 is characterized in that, the described unit that is provided with comprises:
First is provided with module, and when being used for normally or unusually withdrawing from the interface of described single example, described interface rank function lock state is set to not lock state;
Second is provided with module, is used for when described single example of described service end operation normally or unusually withdraws from, and rank function lock state is set to not lock state during described operation.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105634984A CN102025728A (en) | 2010-11-26 | 2010-11-26 | Scheduling method under client-side/server-side architecture and server |
| PCT/CN2011/074204 WO2012068840A1 (en) | 2010-11-26 | 2011-05-17 | Scheduling method and server under client/server architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010105634984A CN102025728A (en) | 2010-11-26 | 2010-11-26 | Scheduling method under client-side/server-side architecture and server |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN102025728A true CN102025728A (en) | 2011-04-20 |
Family
ID=43866582
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010105634984A Pending CN102025728A (en) | 2010-11-26 | 2010-11-26 | Scheduling method under client-side/server-side architecture and server |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN102025728A (en) |
| WO (1) | WO2012068840A1 (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102355423A (en) * | 2011-10-19 | 2012-02-15 | 迈普通信技术股份有限公司 | Forwarded resource access method and routing system |
| WO2012068840A1 (en) * | 2010-11-26 | 2012-05-31 | 中兴通讯股份有限公司 | Scheduling method and server under client/server architecture |
| CN102761604A (en) * | 2012-06-11 | 2012-10-31 | 深圳中兴网信科技有限公司 | Request processing system, request processing method and server |
| CN104159142A (en) * | 2014-08-06 | 2014-11-19 | 乐视网信息技术（北京）股份有限公司 | Video soft decoding method and device of equipment |
| CN109725950A (en) * | 2018-12-29 | 2019-05-07 | 武汉斗鱼网络科技有限公司 | A kind of method, apparatus and storage medium for realizing the operation of client list example |
| CN113240383A (en) * | 2021-04-30 | 2021-08-10 | 江苏康众汽配有限公司 | SAAS management system based on automobile distribution service |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101355775A (en) * | 2008-08-15 | 2009-01-28 | 中兴通讯股份有限公司 | Apparatus for leading configuration data with batch and mutual exclusion method for multi-client terminal |
| CN101364230A (en) * | 2008-09-24 | 2009-02-11 | 金蝶软件（中国）有限公司 | Concurrent access control method and device |
| WO2010062064A2 (en) * | 2008-11-03 | 2010-06-03 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling access to resources in remote user interface service |
| CN101753552A (en) * | 2008-12-01 | 2010-06-23 | 鸿富锦精密工业（深圳）有限公司 | Network communication system and method |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102025728A (en) * | 2010-11-26 | 2011-04-20 | 中兴通讯股份有限公司 | Scheduling method under client-side/server-side architecture and server |
-
2010
- 2010-11-26 CN CN2010105634984A patent/CN102025728A/en active Pending
-
2011
- 2011-05-17 WO PCT/CN2011/074204 patent/WO2012068840A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101355775A (en) * | 2008-08-15 | 2009-01-28 | 中兴通讯股份有限公司 | Apparatus for leading configuration data with batch and mutual exclusion method for multi-client terminal |
| CN101364230A (en) * | 2008-09-24 | 2009-02-11 | 金蝶软件（中国）有限公司 | Concurrent access control method and device |
| WO2010062064A2 (en) * | 2008-11-03 | 2010-06-03 | Samsung Electronics Co., Ltd. | Method and apparatus for controlling access to resources in remote user interface service |
| CN101753552A (en) * | 2008-12-01 | 2010-06-23 | 鸿富锦精密工业（深圳）有限公司 | Network communication system and method |
Non-Patent Citations (2)
| Title |
|---|
| 陆霞敏: "TMN中配置管理子系统的设计与实现", 《计算机技术与发展》, vol. 16, no. 7, 5 July 2006 (2006-07-05), pages 172 - 173 * |
| 陆霞敏: "TMN中配置管理子系统的设计与实现", 《计算机技术及发展》, vol. 16, no. 7, 5 July 2006 (2006-07-05), pages 172 - 173 * |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012068840A1 (en) * | 2010-11-26 | 2012-05-31 | 中兴通讯股份有限公司 | Scheduling method and server under client/server architecture |
| CN102355423A (en) * | 2011-10-19 | 2012-02-15 | 迈普通信技术股份有限公司 | Forwarded resource access method and routing system |
| CN102355423B (en) * | 2011-10-19 | 2013-11-27 | 迈普通信技术股份有限公司 | Forwarded resource access method and routing system |
| CN102761604A (en) * | 2012-06-11 | 2012-10-31 | 深圳中兴网信科技有限公司 | Request processing system, request processing method and server |
| CN102761604B (en) * | 2012-06-11 | 2015-06-17 | 深圳中兴网信科技有限公司 | Request processing system, request processing method and server |
| CN104159142A (en) * | 2014-08-06 | 2014-11-19 | 乐视网信息技术（北京）股份有限公司 | Video soft decoding method and device of equipment |
| CN109725950A (en) * | 2018-12-29 | 2019-05-07 | 武汉斗鱼网络科技有限公司 | A kind of method, apparatus and storage medium for realizing the operation of client list example |
| CN113240383A (en) * | 2021-04-30 | 2021-08-10 | 江苏康众汽配有限公司 | SAAS management system based on automobile distribution service |
| CN113240383B (en) * | 2021-04-30 | 2024-04-05 | 江苏康众汽配有限公司 | SAAS management system based on automobile accessory business |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2012068840A1 (en) | 2012-05-31 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103782574B (en) | Idempotence for database transactions | |
| CN102025728A (en) | Scheduling method under client-side/server-side architecture and server | |
| CN108134764B (en) | Distributed data sharing and exchanging method and system | |
| CN104168333B (en) | The working method of PROXZONE service platforms | |
| CN109753364A (en) | A kind of implementation method, equipment and the medium of network-based distributed lock | |
| CN105915405A (en) | Large-scale cluster node performance monitoring system | |
| CN110557384A (en) | internet of things management control method based on block chain | |
| CN103488526A (en) | System and method for locking business resource in distributed system | |
| CN104333556B (en) | Based on resource service management system Security Certificate gateway decentralized configuration management method | |
| CN111476171A (en) | Distributed object recognition system and method and edge computing equipment | |
| CN102929696A (en) | Method and apparatus for constructing, submitting and monitoring center node of distributed system | |
| CN110990200A (en) | Flow switching method and device based on multi-activity data center | |
| US9813496B2 (en) | Method and apparatus for collaborating in a work environment | |
| CN107992491A (en) | A kind of method and device of distributed file system, data access and data storage | |
| CN112905364A (en) | Calling method of micro service and electronic equipment | |
| CN107395717A (en) | A kind of method that free time time-out applied to O＆M auditing system disconnects automatically | |
| CN102916830A (en) | Implement system for resource service optimization allocation fault-tolerant management | |
| CN206498429U (en) | A kind of Core server group network system based on distributed heterogeneous network | |
| CN106656584A (en) | Method for judging invalid nodes of distributed system | |
| CN100413248C (en) | Improved method and system for carrying out charging based on flow | |
| CN111190913A (en) | Distributed lock implementation method and system | |
| US10674337B2 (en) | Method and device for processing operation for device peripheral | |
| CN105025110B (en) | A kind of multi-client data changes the accurate method for pushing of message | |
| CN101145965A (en) | A method and device for automatic login to telecommunication network management | |
| CN111722988A (en) | Fault switching method and device for data space nodes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Application publication date: 20110420 |