HTTP version compatibility

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Does anyone know if there's any issues involving versions of .Net Framework,
Visual Studio and HTTP which might cause a compatibility problem?
We currently using VS1.1 for our web apps (C#) and the app seems to be up
and and down quite regularly on production and we're not quite sure why. Our
techies told us that because we're (developers) using the wrong version of
http, 1 instead of 1.1, which cause some sort of compatibility issues and/or
memory leaks...blah blah blah.
Without going into too much details and politics, I just like to know if
there's any connections between Visual Studio versions, .Net Framework and
the http versions which might cause compatibility issues.

Any suggestion is greatly appreciated.
Calvin
 
Thus wrote Calvin,
Does anyone know if there's any issues involving versions of .Net
Framework,
Visual Studio and HTTP which might cause a compatibility problem?
We currently using VS1.1 for our web apps (C#) and the app seems to be
up
and and down quite regularly on production and we're not quite sure
why. Our
techies told us that because we're (developers) using the wrong
version of
http, 1 instead of 1.1, which cause some sort of compatibility issues
and/or
memory leaks...blah blah blah.
Click to expand...

HTTP 1.0 cannot cause memory leaks. It's just a protocol. But I agree that
using HTTP 1.0 should be avoided, as it lacks important features like controlling
caches.
Without going into too much details and politics, I just like to know
if
there's any connections between Visual Studio versions, .Net Framework
and
the http versions which might cause compatibility issues.
Click to expand...

Not that I know of, neither client (System.Net) nor Server (System.Web).

Cheers,
 
Back
Top