Connected vs Disconnected Architecture in asp.net

Question

what are advantages & disadvantages of connected & disconnected Architecture (database) over one another in asp.net ?

Answer 1

asp.net is a server side technology designed for a server to process requests for pages. The very nature of ASP.NET requires a connected model.

Could you clarify what you mean by "disconnected"?

Answer 2

With regards to ASP.NET, a "disconnected" architecture usually refers to one in which data is downloaded to the ASP.NET app's memory in infrequent bulk requests and stored in the cache for later processing. This avoids frequent trips to the database, thus eliminating one of the major I/O obstacles. In a site where data is frequently queried but not updated, this can be a significant performance improvement, if your server has the memory to support the caching of the data.

There is of course the possibility that you're referencing the use of something like Google Gears, but I haven't heard of that being used much in the ASP.NET world. Anything's possible, I suppose.