Archived Forum Post

Index of archived forum posts


When does a GET request end an Azure instance?

Nov 28 '12 at 00:37

Here's a really silly question. I'm using ChillKat to send a GET request to my Azure cloud service. But since you pay for instances, I don't want the instance to be up any longer than it needs to. So, when does an instance, or a GET, end?

If you do it manually on the URL address bar of your browser you can be sure the get has ended when you close the browser. But if the GET comes from a program?

Maybe someone here has already done this...?

Maybe there is a function in ChilKat which ends a connection and that would end the instance?


I don't know what it means from Azure's point of view, meaning I don't know the meaning of an "Azure instance". One sure-fire way to make sure everything is close is to call the Chilkat.Http.CloseAllConnections method after doing the GET.


After several confusing answers on the Azure forums Steve Marx posted this:

"I think there's some confusion. Making the GET request doesn't create any instances of your web role. You tell Windows Azure how many instances of your web role you want when you deploy your application. Unless you change that number, it will stay constant.

Think of an instance as a server (or VM). You decide how many servers you need, and Windows Azure runs them for you. When you make a GET request, it goes to one of the servers and is handled there. Depending on what your application does, a single instance might be able to handle hundreds of requests per second."

So that is good, plus I'll implement the Chilkat.Http.CloseAllConnections suggestion.