Then you could use a Hashtable. Be sure to serialize writing (when users log in/out)to it with a lock.
You are saying "it will constantly be adding and reading data into it.". By it you mean the "DataClass" per client? not the hashtable I assume... You could see the "DataClass" as what Session is in asp.net. Its store all info of a single client/user. The hashtable is just a container of these session objects for fast lookup of the clients session. And what performance concerns, always measure you app before implementing any optimizations ;) HTH // Ryan =================================== This list is hosted by DevelopMentor� http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
