In this chapter, we definitely uncovered a lot of interesting aspects of disconnected Web applications. Since data is rarely read-only, we focused on the batch update. ADO.NET provides much more flexibility than ADO when conducting a batch update. You can write application-specific commands for the INSERT, DELETE, and UPDATE operations, and you can control more closely how conflicts are generated and resolved.
In ADO.NET, you can run a batch update with rules you bolt onto the code yourself and never raise a single conflict. This is probably the easiest route to take, requiring you only to write custom commands and preventing you from relying on system-provided command builders. If you choose to use command builders, you must be ready to handle conflicts and deal with the in-memory commit mechanism and process resumption.