Comments by Member 11318373 (Top 2 by date)

Member 11318373 24-Sep-15 11:23am View

thank you. I have now a clearer idea of how the work requests and I will consider your recommendations

Member 11318373 21-Sep-15 16:43pm View

Deleted

I have a service API using ASP.NET MVC 4 and Web API and I need to handle shipping stored in a database images.

My intention was to manage lists, that is, put all the images that I can return a query in a list of type string, for this I make the array of bytes to get from the query image and transform a string using Convert.ToBase64String .

So making a single request, the Web Service returns me the list to the client and manage images displayed in an application. The detail here is that I realized that there is a maximum limit of memory you can use an application (I'm not sure how, I just do not allow many images) and can not always send all images in a list.

So I came up image by image by sending a request by each, but what if there are 20 pictures to send ?, 20 requests would be made; and if they are 10 users who need to download information 20 images each, would be 200 requests.

My question is, what will happen to the server, collapse or what ?, how correct is the way I'm using for sending images, lists (although I do not think it serves me well) or by image ?, Why would I do if taking 10 of the 20 files downloaded to the network connection is lost ?, Is there a way to do this without so many requests? and if could someone explain how the web service works in terms of resources used or is an IIS problem (which incidentally I'm using it to publish the web service).