Re: Apache vs IIS

Hi

"J.O. Aho" <user@xxxxxxxxxxx> skrev i meddelandet
news:632nggF25ve0oU1@xxxxxxxxxxxxxxxxxxxxx
Lars wrote:

From what I have read and been told ASP.NET has the ability to tell how
to manage SESSION cockies for a particular site. I know you can set this
up in Apache but I recall that is for the entire webserver.

Apache/PHP allows you to set session cookies for a whole site, or part of
a site if so wanted. Multi-domain sessions are a bit more difficult, but
possible. So you don't recall it correctly.


By using SESSION cockies in ASP.NET you can save a lot of processing on
the server.

Sure, as long as file I/O ain't causing you the trouble, or if storing in
memory that the RAM don't run out.

The key is that information is stored on the clients computer and the client
application doesn't need to call the server for every interaction with the
page. If you have a page you interact often with, let's say every 10 second.
YOu can set the OutputCache in ASP.NET to let's say 15 seconds. Then the
page wouldn't be regenerated after only 10 seconds. This save time consuming
calls to databeses and other tasks. This since the same information
shouldn't have to be send over and over again. As I understand to do this in
PHP you have to store the values in SESSION cockies then check the SESSION
array to see if the value was stored or not. ASP.NET takes care of all this.

Remember that ASP.NET sends back HTML code that includes Java Scripts. I
don't think you even net the .NET framework installed to view the page. Only
to develop the page and run .NET application.



Lars





--

//Aho


.

Quantcast