Skip to main content

Dictionary - custom key type

In ultimele 2 saptamani am luat la puricat .NET Collections si m-am gandit ca merita sa vorbim astazi putin despre cheile unui dictionar( Dictionary) - map.
In general lucram cu chei care sunt de tip value type.

Dictionary<int, Door> map = new Dictionary<int, Door>();
map.Add(1,door1);
map.Add(2,door2);
...
var door1 = map[1];
In acest caz, cheia o sa fie gasita fara nici o problema. Dar ce se intampla cand cheia noastra este reprezentata de un tip declarat de noi?
Dictionary<DoorKey,Door> map = new Dictionary<DoorKey, Door>();
map.Add(doorKey1, door1);
map.Add(doorKey2, door2);
....
var door1 = map[copyOfDoorKey1];
In momentul cand o sa dorim sa facem retrive la element pe baza de cheie, o sa observam ca elementul nu este gasit( o eroare de tip KeyNotFoundException o sa fie aruncata). In debug daca ne uitam la ce elemente contine dictionarul, o sa observam ca avem doua elemente cu cheiule pe care le-am astepta, dar totusi nu putem sa facem retrive la date.
Fiecare colectie de tip (cheie,valoare) are implementari diferete, dar in general una sau mai multe elemente sunt grupate intr-un bucket( galeata), pe baza la hash code. Dimensiunea sau distributia pe valori a acestuia difera, dar ce trebuie sa retinem aici este ca fiecare element este adaugat intr-un anumit bucket pe baza unui hash returnat de catre cheie. Dupa ce este identificat bucket-ul, se face o cautare a cheii in bucket-ul respectiv pe baza metodei Equal.
Indiferent de metoda de implementare a dictionarului, cautarea se face pe baza acestor doua metode. Din acesta cauza, in exemplul dat mai sus o sa ne trezim ca elementul nu este gasit niciodata, chiar daca teoretic in colectie avem cheie data.
Pentru toate tipurile de date pe care o sa le folosim pe post de cheie, este nevoie sa facem override la GetHashCode si Equal. Mai jos putem sa gasim un exemplu pentru clasa DoorKey
class Doorkey
{
    int RoomNumber { get; set; }
    int DoorNumber {get; set; }
    public override bool Equals(object obj)
    {
        if( obj == null
            || !( obj is DoorKey ))
        {
            return false
        }
        return RoomNumber == obj.RoomNumber
            && DoorNumber == obj.DoorNumber
    }
    public override int GetHashCode()
{
    return RoomNumber.GetHashCode();
}
}
Pentru metoda GetGashCode, aceasta nu este cea mai buna implementara. Cea mai importanta regula pe care metoda GetHashCode trebuie sa o respecte este ca valoarea returnata sa fie aceiasi pentru un obiect care are aceiasi stare( valoare).
Asa ca, de fiecare data cand lucram cu dictionarele( maps) din .NET, iar cheile sunt reprezentate de tipuri custom, nu trebuie sa uitam sa facem ovveride la GetHashCode si Equals, in caz contrat o sa ne trezim ca nu putem sa obtinem datele pe baza cheii.

Comments

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