1

Topic: Inquiry: How to name "Distributed Singleton"

P.S. The most interesting did not get into inquiry: the Technically-descriptive synonym - Distributed Single Worker. The feature simple - on all clones () is guaranteed that the given code, more precisely, the flow or some flows, are fulfilled only in one . A clone - a keyword. I.e. both the code and configs on all  the identical. But the given logical flow always is fulfilled only on one . Such tasks full in any service - mailing  and letters on conditions in preset time, replication in/from external systems and so forth Here in connection with ease of cloning  and in clouds at myself" dll-ku also I think as to name. It is a question about ready implementation, a packet Name, dll, , a post in  and so forth Offer variants who is able. P.P.S. It was necessary in architecture http://rsdn.ru/poll/5374 the Author: VladCore Date: 24.06 09:24 Question: In connection with simplicity of cloning  in clouds  conditionally named Distributed Singleton. I can not invent a title. It is such flow which only on one  it is executed. Who is able to invent titles, add the variants. A word single or the synonym is almost assured of a title should be mandatory.

2

Re: Inquiry: How to name "Distributed Singleton"

Hello, VladCore, you wrote: VC> Offer variants who is able. As always: we describe the decision (43, aha), the task it is not sounded, we ask comments What comments here can be?  the task should be described, then the reality will be. If speech about a hot reserve that at service falling quickly to restart on other copy it hot spare / failower / AlwaysOn is normally called.

3

Re: Inquiry: How to name "Distributed Singleton"

Hello, VladCore, you wrote: VC> the Feature simple - on all clones () is guaranteed that the given code, more precisely, the flow or some flows, are fulfilled only in one . A clone - a keyword. I.e. both the code and configs on all  the identical. But the given logical flow always is fulfilled only on one . Such tasks full in any service - mailing  and letters on conditions in preset time, replication in/from external systems and so forth it is not clear that you do (I full  in WCF), but: distributed (distributed) is an antonym to that that you do (lock all while the flow is occupied?), singleton - widespread concept even if you use a pattern ,  to use this word good idea. From this that I understood you do certain manager (dispatcher?) . I would look synonyms to this word. Probably you use any technics to reach wished, in this case name library "Kakaja-to_tehnika Thread (Task? Logical Thread? Clone Job?) Dispatcher".

4

Re: Inquiry: How to name "Distributed Singleton"

Hello, Sinix, you wrote: VC>> Offer variants who is able. S> as always: we describe the decision (43, aha), the task it is not sounded, we ask comments the Task quite clearly wrote - to Invent a title under the description. S> what comments here can be?  the task should be described, then the reality will be. If speech about a hot reserve that at service falling quickly to restart on other copy it hot spare / failower / AlwaysOn is normally called. , Charles!

5

Re: Inquiry: How to name "Distributed Singleton"

Hello, Sinatr, you wrote: S> Hello, VladCore, you wrote: VC>> the Feature simple - on all clones () is guaranteed that the given code, more precisely, the flow or some flows, are fulfilled only in one . A clone - a keyword. I.e. both the code and configs on all  the identical. But the given logical flow always is fulfilled only on one . Such tasks full in any service - mailing  and letters on conditions in preset time, replication in/from external systems and so forth S> it is not clear that you do (I full  in WCF), but: distributed (distributed) is an antonym to that that you do (lock all while the flow is occupied?) I will tell it is not a pity.  there are two   on the redis-server about that that candidates did not fall and are not ungeared and about that that singleton is successful without  operation works. Still there are choices when the elite earlier singleton fell. Choices are certainly fulfilled under DistributedLock th. S> singleton - widespread concept even if you use a pattern ,  to use this word good idea. The dictionary with you does not agree S> From this that I understood you do certain manager (dispatcher?). I would look synonyms to this word. Probably you use any technics to reach wished, in this case name library "Kakaja-to_tehnika Thread (Task? Logical Thread? Clone Job?) Dispatcher ". The word the manager for public  is not pleasant to me, but I did not invent the best. You almost guessed all under the description. Here so looks  in the application-oriented code: class Worker {readonly ManualResetEvent ProcessShutdown = GetProcessShutdown (); public void ThreadStart () {var manager = new DistributedSingletonManager (......); while (! ProcessShutdown. WaitOne (1000) && manager. Am_I_TheOne (timeout: 1000)) {PerformSomething ();}}} ThreadStart it is launched on all , and here PerformSomething () in a cycle spins always only on one. If it is necessary choices new  as"are launched"what unique will do operation PerformSomething () Here now a title I invent. Inside is DistributedLock, not I invented it. Here also took DistributedSingleton is exceptional by analogy with DistributedLock

6

Re: Inquiry: How to name "Distributed Singleton"

7

Re: Inquiry: How to name "Distributed Singleton"

8

Re: Inquiry: How to name "Distributed Singleton"

Hello, VladCore, you wrote: VC> Here also took DistributedSingleton is exceptional by analogy with DistributedLock Ugu typical failover with hot sparing. Well, or very much the special case load balancer that at you under a cowl there distributed lock it is pure an implementation detail (which also exchanges in due course most likely). At the same time, your client API interests at all details (lock), to it it is important "that did that is necessary to me". And on it "that is necessary to me" it and will search. What chances to be will be if to call the refrigerator "the device on change of a modular state of a coolant", to estimate simply. Therefore, if the title with pathos - something of type AlwaysOnline is necessary. FailowerDispatcher. If without - to search on keywords and to look, how it at people is called.

9

Re: Inquiry: How to name "Distributed Singleton"

Hello, VladCore, you wrote: VC> the Technically-descriptive synonym - Distributed Single Worker. The feature simple - on all clones () is guaranteed that the given code, more precisely, the flow or some flows, are fulfilled only in one . A clone - a keyword. I.e. both the code and configs on all  the identical. But the given logical flow always is fulfilled only on one . Such tasks full in any service - mailing  and letters on conditions in preset time, replication in/from external systems and so forth Is interesting for what it is necessary, that in one copy? The same sending , letters and an other crap can be executed in any amount of copies, principal that the letter has not been sent twice. For this purpose there are quite clear mechanisms of operation. And here the implementation detail, and not the most successful which sticks out outside turns out. And it is not clear as at it with fail safety.