WCF static method in class

Question

I am designing a WCF web service that will potentially be called 10,000+ plus individual clients at any given time. When the service is called, the service creates the class Object1.

public List<string> AnswerClient() { Object1 _hello = new Object1(); return _hello.AnswerClient(); } 

Since the class Object1 must create other classes Object1 inside it. He needs to create other subsets of the Object1 classes. I was thinking about using a static method in the Object1 class to create other Object1 methods, such as

 Object1.AnswerClient() 

because I don’t think I need to create a specific Object1 () in the first place. If multiple clients call the service, will this Object1.AnswerClient () ruin the code because it is static? Since statics are class specific, do all clients seem to be affected?

How do I create this class. The client calls the service, the service creates an object based on client data. This object inside it creates another 20 similar objects (splits user data depending on the data).

Any help and understanding will help. How should I do this at all?

Thanks.

Answer 1

I suggest you take a look at the Factory design template to do what you described above.

Answer 2

If the AnswerClient method itself does not require any state other than the state that it creates, then there should be no problems with its statics.

Speaking of this, I thought of it differently. Is AnswerClient something that is a function of Object1 (which can also get a better name)? Or is it a universal utility method? If it is logically bound to a specific instance of "Object1", I left it as an instance method. If this is a more general utility and is not directly related to what "Object1" is, make it static.