Skip to main content

ReadOnlyDictionary in .NET 4.0 and 4.5

.NET 4.5 aduce destul de multe feature noi. Insa pana o sa fie adoptat pe proiectele in curs o sa treaca o perioada destul de lunga. Unele din aceste feature le putem avea si in .NET 4.0, doar ca trebuie sa scriem putin cod.
In .NET 4.5 daca avem nevoie de un dictionar care sa fie read-only este destul de simplu. Avem la dispozitie interfata IReadOnlyDictionary si implementarea acesteia. Implementarea poate sa fie gasita in namespace-ul System.Collections.Generic din 4.5.
Dictionary<int, string> dictionary = new Dictionary<int, string>();
dictionary.Add(1, "first");
dictionary.Add(2, "second");

ReadOnlyDictionary<string, int> readOnlyDictionary =
new ReadOnlyDictionary<string, int>(dictionary);

Ce este bine de stiut ca operatiile de add/edit/delete inca exista, doar ca in momentul in care acestea o sa fie apelate o sa arunce o exceptie de tip NotSupportedException.
Daca ati lucrat cu API-ul de Team Foundation, ati putut observa ca exista deja o implementare pentru acesta colecție. La fel si in API-ul de la Office 2007.
Daca nu lucram cu API-uri care au deja implementari a unui dictionar read-only, putem sa ne definim noi propia implementare. Tot ce trebuie sa facem este sa implementam interfata IDictionary care sa accepte in constructor un dictionar sau o colectie de elemente . Toate metodele care permit adaugare, modificare sau editare de elemente din dictionar nu trebuie implementate.
O alta varianta este sa va definiti si o interfata de tip IReadOnlyDictionary, care sa permita doar acces la date.
Mai jos puteti sa gasiti o implementare a unui ReadOnlyDictionary, implementand direct interfata IDictionary.
  public class ReadOnlyDictionary<TKey, TValue> : IDictionary<TKey, TValue>
{
private const string NotsupportedExceptionMessage = "This dictionary is read-only";

private readonly IDictionary<TKey, TValue> _dictionary;

public ReadOnlyDictionary(IDictionary<TKey, TValue> dictionary)
{
_dictionary = dictionary;
}

public void Add(TKey key, TValue value)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public bool ContainsKey(TKey key)
{
return _dictionary.ContainsKey(key);
}

public ICollection<TKey> Keys
{
get { return _dictionary.Keys; }
}

public bool TryGetValue(TKey key, out TValue value)
{
return _dictionary.TryGetValue(key, out value);
}

public bool Contains(KeyValuePair<TKey, TValue> item)
{
return _dictionary.Contains(item);
}

public void CopyTo(KeyValuePair<TKey, TValue>[] array, int arrayIndex)
{
_dictionary.CopyTo(array, arrayIndex);
}

public int Count
{
get { return _dictionary.Count; }
}

public bool IsReadOnly
{
get { return true; }
}

public TValue this[TKey key]
{
get
{
return _dictionary[key];
}
set
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}
}

public IEnumerator<KeyValuePair<TKey, TValue>> GetEnumerator()
{
return _dictionary.GetEnumerator();
}

System.Collections.IEnumerator System.Collections.IEnumerable.GetEnumerator()
{
return (_dictionary as System.Collections.IEnumerable).GetEnumerator();
}

public bool Remove(TKey key)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public void Add(KeyValuePair<TKey, TValue> item)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public void Clear()
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public bool Remove(KeyValuePair<TKey, TValue> item)
{
throw new NotSupportedException(NotsupportedExceptionMessage);
}

public ICollection<TValue> Values
{
get { throw new NotSupportedException(NotsupportedExceptionMessage); }
}
}


Comments

  1. Interesant - sau cine e mai lenes, va folosi o implementare gata facuta, precum GuardedDictionary din C5 collections: http://www.itu.dk/research/c5/

    ReplyDelete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP