New answers tagged

1

The article you linked to is using Tasks, you should should do that too, instead of BackgroundWorkder. There are many reasons why Tasks are preferable, Stephen Cleary has a series of articles explaining why.


1

If I understand this correctly you have a long list of methods that should be called sequentially. But you would like to be able to pause the execution between each call to a method, but you do not now where beforehand. An algorithm like this might do the trick public void MyTaskMethod() { List methodObjList = GetListOfMethodObjs(); foreach(var ...


0

You have to identify each client - this might be IP address or a session ID passed in on every call or an authenticated token. You store the properties either in memory or in a persisted store such as a database. You need to look up the properties on each request by the passed in identification. So, all's simple and good as you now have a collection of ...


0

I think that you have to stand back and consider where you are going to persist the properties. The obvious place is in a database table indexed on clientID. How you map these properties to classes is a problem long solved by ORM frameworks (e.g. MyBatis and Hibernate in the Java space). It is highly unlikely that your properties will end up as static ...



Top 50 recent answers are included