Skip to main content

Convert a stream to a byte array

De cate ori nu v-ati lovit de cerinta urmatoare:
Sa se converteasca un stream intr-un sir de bytes.
Am vazut diferite implementari la aceasta solutie. Cea mai comuna este cea in care se itereaza prin stream.
byte[] bytes = new byte[10000];
int temp;
int offset;
while ((temp = ms.Read(bytes, offset, bytes.Length - offset)) > 0)
{
     offset += temp;
}
Aceasta solutie o sa functioneze, dar putem sa ne folosim si de alte functii, care sa simplifice putin codul si sa eliminam sansele ca un bug sa apara.
O alta varianta este sa folosim metoda GetBuffer. Aceasta ne returneaza sirul de bytes din care a fost creat streamul. Trebuie avut grija la doua lucruri aici:
  1. nu se face o copie a sirului de bytes
  2. lungimea sirului care ne este returnat nu reprezinta lungimea reala a streamului. De exemplu daca avem un stream de 10 bytes si apelam GetBuffer, o sa ne fie returnat un sir de lungime 256 din care 246 de elemente nu sunt folosite.
byte[] bytes = ms.GetBuffer();
Ultima solutie pe care o propun, este sa apelam metoda ToArray(). Prin acest mod o sa ne fie returnat un sir de lungime egala cu numarul de bytes din stream si totodata se genereaza o copie a sirului original. Nu trebuie sa ne facem griji ce se intampla daca continutul stream-ului se modifica. Trebuie stiut ca nu conteaza daca din stream s-a facut citire sau nu, ToArray() ne va returna tot sirul de bytes, indiferent de pozitia cursorului.
MemoryStream ms = new MemoryStream(new byte[]{0,1,2,3,4});
var toArray1 = ms.GeArray(); // Lungime sir returnat = 5
ms.ReadByte()
var toArray2 = ms.GeArray(); // Lungime sir tot returnat = 5

Enjoy!

Comments

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...

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

AI ROI without hype: a practical way to measure value using risk adjustment + Azure Copilot example

Most people know what ROI means, but it’s harder to calculate for AI projects. The numbers are less predictable than with traditional platforms because many AI projects never reach stable production. IDC says only about 44% of custom AI apps and 53% of third-party AI apps make it from proof of concept to production. That’s why it’s important to look at ROI through a risk lens, not just cost versus benefit. One useful approach is to use a risk-adjusted formula: AI ROI = (AI Business Value Income / (Initial Investment + Annual Costs)) × Success Probability where, >AI Business Value Income (over N years) Consider a 2 to 3 year period and include both direct and indirect value: Direct: time saved, fewer tickets, higher conversion, lower fraud. Indirect: improved customer or employee experience and quicker decisions. For these, use measurable stand-ins like CSAT, churn, time to resolution, or hours saved, and estimate conservatively. >Initial Investment This covers more than just buil...