C#: "Using" Statements with HttpWebRequests/HttpWebResponses

Question

Jon Skeet made a comment (via Twitter) on my SOApiDotNet code (a .NET library for the pre-alpha Stack Overflow API):

@maximz2005 One thing I've noticed just from browsing the source quickly: you don't disposed (sic) of WebResponses. "using" statements FTW.

He indicates that I need to wrap these Web sessions in "using" statements. However, I have a question about this: should I wrap the whole thing, starting with the HttpWebRequest, or should I create the WebRequest outside of the "using" statement and then wrap the Response inside? I have a feeling that the difference is that, in the former, both objects would be disposed of - is this correct?

Thanks in advance.

score 50 · Accepted Answer · edited Apr 05 '12 at 11:53

50

HttpWebRequest itself is not disposable unlike HttpWebResponse. You should wrap disposable resources with using to allow early and determined cleanup. Correctly implemented IDisposable pattern allows multiple calls to Dispose without any issues so even the outer using statement wraps resource that during its own dispose disposes inner using statement resource it is still ok.

Code example

var request = (HttpWebRequest)WebRequest.Create("example.com"); 
using (var response = (HttpWebResponse)request.GetResponse()) 
{ 
    // Code here 
}

edited Apr 05 '12 at 11:53

Michał Powaga

22,561
8
51
62

answered Dec 28 '09 at 08:28

Dzmitry Huba

4,493
20
19

So should I declare ..Request outside, or what? – Maxim Zaslavsky Dec 28 '09 at 08:33
2

Yes, that means you'd do a var request = (HttpWebRequest)WebRequest.Create("http://example.com"); using (var response = (HttpWebResponse)request.GetResponse()) { // Code here } – Benjamin Podszun Dec 28 '09 at 08:50
1

@Dzmitry, @Benjamin. I added Benjamin's code example to your answer. – Jan Jongboom Dec 28 '09 at 09:03

Benjamin Podszun · Answer 2 · 2009-12-28T09:36:32.997

6

Everything wrapped in a using () {} block (that is, inside of the first brackets) is disposed when you leave the scope.

I haven't used your library so far (seems nice though), but I'd argue that you should explicitly dispose every IDisposable you create (= are responsible for) and don't return to a caller.

A sidenote, since I've seen a lot of people struggling with multiple things to dispose: Instead of

using (var foo = SomeIDisposable) {
  using (var bar = SomeOtherIDisposable) {
  }
}

which needs a lot of vertical space you can write

using (var foo = SomeIDisposable)
using (var bar = SomeOtherIDisposable) {
}

edited Dec 28 '09 at 09:36

answered Dec 28 '09 at 08:27

Benjamin Podszun

9,679
3
34
45

Your second paragraph (which is correct, I believe) contradicts the first. If everything inside the using-block is disposed, you wouldn't need the inner using statement. – Tomas Dec 28 '09 at 09:17
See my updated post: Everything inside of using (...) is disposed when you leave the following block (this part: { ... }) – Benjamin Podszun Dec 28 '09 at 09:37

score 1 · Answer 3 · answered Dec 28 '09 at 09:09

1

In order to prevent memory leaks you should call Dispose on every object that implements IDisposable. You can ensure that the Dispose method in called by using the using keyword (no pun intended) as it is just a syntactic sugar for try-finally block.

answered Dec 28 '09 at 09:09

Giorgi

30,270
13
89
125

C#: "Using" Statements with HttpWebRequests/HttpWebResponses

3 Answers3

Linked

Related