>Distributted computing is a design decision as much as it is a physical disconnected issue. I think you're taking things way to literal.
>
>Today's real systems are Web based and will need to deal with connectivity issues. By building apps this way even if they're not disconnected the disconnected functionality can basically be plugged in at will...
>
>It's not for everybody, but it's a great way to have real reason to build n-Tier systems, because distributdd computing really doesn't work any other way!

Hi, Rick, Mike.

And if you look at some of the .Net framework you can clearly see what Rick's talkin about.

I'm thinking specifically on things like UpdateGrams in SQL Server 2000. These are designed to handle things like make a request to a DB in Kuala Lumpur on monday, edit it on Montevideo on tuesday, and send the updates on wednesday, and even so having a simple method to control changes made in the meantime.

The whole ADO.Net works all time under these principles.

Is an exciting world outh there...