Skip to main content

How to get a valid daylight saving time - Part 2

Intr-un post anterior am povestim putin despre TimeZone si daily light saving. Prin metoda "IsDaylightSavingTime" a unui TimeZoneInfo spuneam ca se poate verifica daca pentru o anumita data avem ora de vara sau de iarna.
Lucrurile se complica putin cand nu cunoastem TimeZoneInfo pe care il are clientul. In acest caz, pe baza orei trebuie sa identificam pe ce time zone se afla clientul. Acest lucru nu se poate determina in totalitate, dar putem identifica un time zone care partial asemanator.
Un obiect de tip TipZoneInfo contine metoda "GetAdjustmentRules" care ne returneaza o lista de reguli care se folosesc pentru a ajusta ora (de exemplu ora de vara sau de iarna). Fiecare regula defineste perioda de inceput si de sfarsit dar din pacate perioada nu este definita la nivel de zi ci doar de luna. De exemplu ni se specifica ca in luna martie se termina perioada in care se aplica regula, dar nu se specifica data exacta cand aceasta se termina.
A doua problema apare in cazul in care aplicatia ruleaza pe un server care are setat time zone-ul pe "Coordinated Universal Time". Pentru acest time zone nu exista ora de vara sau de iarna, din aceasta cauza incercati sa verificati daca ora data este de vara sau de iarna folosind metoda "IsDaylightSavingTime" o sa va trezici cu rezultate ciudate.
In unele cazuri nu avem altceva de facut decat sa ne vazam de ora pe care clientul o trimite si pe baza careia sa obtinem un time zone. Acesta solutie trebuie aplicata doar daca este ultima solutie, deoarece niciodata nu trebuie sa ne bazam pe ora clientului si sa o comparam cu cea a serverului, dar in unele cazuri aceasta este singura optiune.
Pentru a obtine ultima duminica dintr-o luna va recomand sa folositi urmatoarea metoda:
public static DateTime LastDay(this DateTime current, DayOfWeek dayOfWeek)
{
DateTime lastDay = current.Last();
return lastDay.AddDays(Math.Abs(dayOfWeek - last.DayOfWeek)*-1);
}
Dupa ce comparam ora clientului cu cea a serverului trebuie sa verificam daca data curenta este cu ora de vara sau de iarna. Pentru acest lucru putem sa ne folosim de metoda data mai sus si sa verificam data data este cuprinsa intre ultima duminica din luna Octombrie si ultima duminica din luna Martie.
Acesta nu este cel mai sigur mecanism, dar in unele cazuri poate sa fie singura solutie pentru a putea determina in ce time zone se afla clientul.

Comments

  1. Ciudat.. Cum fiecare tara (culture in .NET terms) poate avea propriile reguli legate de ora de vara, si unele tari sunt in mai multe timezones (GMT+n), nu prea vad cum ai putea afla daca o data&ora e in summer time sau nu fara a sti macar si culture-ul din care provine.. (multe tari de la ecuator sau Rusia nu folosesc DST, evident, chiar daca sunt in GMT+2 de ex).

    Sa nu mai vorbim de ciudateniile din USA, unde state din acelasi timezone folosesc sau nu DST dupa cum cred de cuviinta.. :)

    ReplyDelete

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...