C#

public static List<SocketStructure> GetHostAddressesList() {
  lock(m_locker) 
  {
    List<SocketStructure>tmp = new   List<SocketStructure>();
    for(int i = 0; i<m_HostAddress.Count(); i++)
    {
        SocketStructure s = new SocketStructure();
        s.IP = m_HostAddress[i].IP; 
        s.port =  m_HostAddress[i].port; 
        tmp.Add(s);
    }
    return tmp; // note: not needed to use .ToList() here
  }
}

Member 12061600 wrote:

PS. (Same applies for strings I guess as it does with ints, since string are immutable)

Member 12061600 wrote:

PPS Just started thinking indeed returning reference to object even if you have locks inside getters is rather tricky - because some other thread might change contents of the reference type, and if you are left with the reference which you retrieved above you will see different results depending how other thread modifies it

Member 12061600 wrote:

So when I am returning value types - it is fine?

Member 12061600 wrote:

But if I return reference type I better make a deep copy, that is better practice you say right?

struct socket {
  string ip;
  int port;
}

Member 12061600 wrote:

I will stick to my approach then ...

1. If the path does not exist in the database, you know you're going to need to check it.
2. If the path does exist, compare the actual file length against the one you stored in the database. If it differs, you're going to need to check it.
3. Assuming you've reached this point, you're going to have to hash the physical file and then compare it against the hash you've stored. Again, if it differs, you're going to need to check the file.