Best Practices for System.Net Classes what?

[Janus Knudsen]

Hello...

Need a little explanation!

Snippet from MSDN:
"The following recommendations will help you use the classes contained in
System.Net to their best advantage:

Use WebRequest and WebResponse whenever possible instead of type casting to
descendant classes. Applications that use WebRequest and WebResponse can
take advantage of new Internet protocols without needing extensive code
changes. "

Well, it's recommended that you dont type cast to descendant classes - but
what does that mean?

And what classes it referring to?

Regards
Janus

[DalePres]

The most common derived classes are HttpWebResponse and HttpWebRequest
classes that are the base for the Page.Request and Page.Response objects
that you no doubt use regularly in ASP.Net.

Dale

"Janus Knudsen" <[e-mail]> wrote in message
news:%2*****************@TK2MSFTNGP12.phx.gbl...

Hello...

Need a little explanation!

Snippet from MSDN:
"The following recommendations will help you use the classes contained in
System.Net to their best advantage:

Use WebRequest and WebResponse whenever possible instead of type casting to descendant classes. Applications that use WebRequest and WebResponse can
take advantage of new Internet protocols without needing extensive code
changes. "

Well, it's recommended that you dont type cast to descendant classes - but
what does that mean?

And what classes it referring to?

Regards
Janus

[Joerg Jooss]

DalePres wrote:

The most common derived classes are HttpWebResponse and HttpWebRequest
classes that are the base for the Page.Request and Page.Response
objects that you no doubt use regularly in ASP.Net.

No, they're not. These classes are used on the client-side. Page.Request and
Page.Response are instances of System.Web.HttpRequest and
System.Web.HttpResponse respectively.

Cheers,

--
Joerg Jooss
jo*********@gmx.net

[Joerg Jooss]

Janus Knudsen wrote:

Hello...

Need a little explanation!

Snippet from MSDN:
"The following recommendations will help you use the classes
contained in System.Net to their best advantage:

Use WebRequest and WebResponse whenever possible instead of type
casting to descendant classes. Applications that use WebRequest and
WebResponse can take advantage of new Internet protocols without
needing extensive code changes. "

Well, it's recommended that you dont type cast to descendant classes
- but what does that mean?

It means that doing

HttpWebRequest request
= (HttpWebRequest) WebRequest.Create(http://localhost/page.aspx);

is bad... which of course is utter rubbish when you really need to use
low-level technical properties that are only exposed by HttpWebRequest.

Cheers,

--
Joerg Jooss
jo*********@gmx.net

[DalePres]

Whoops... My mistake. Thanks

"Joerg Jooss" <jo*********@gmx.net> wrote in message
news:OV**************@TK2MSFTNGP09.phx.gbl...

DalePres wrote:

The most common derived classes are HttpWebResponse and HttpWebRequest
classes that are the base for the Page.Request and Page.Response
objects that you no doubt use regularly in ASP.Net.
No, they're not. These classes are used on the client-side. Page.Request

and Page.Response are instances of System.Web.HttpRequest and
System.Web.HttpResponse respectively.

Cheers,

--
Joerg Jooss
jo*********@gmx.net