What does IcePatch2-Client if the connection to IcePatch2-Server breaks?

[Ewgenijkkg]

That's my question What I'm interested in is, what happens with the client data repository. Imagine the following scenario:

The client connects with the server and sees that it has to update four of its files: one, two, three and four. It transferes the first two files: one and two. Then the connection breaks due to some nasty reason. What happens then? Does the client repository contain the new version of one and two, while it contains the older one of the files three and four? If so, then the state of the client repository would be inconsistent. Or will the changes made to one and two be undone, so the client has a valid (consistent) state of the repository with the old versions of all four files?

And what happens, if the client repository was empty before the client started patching?

Regards
Ewgenij

[matthew]

If the connection is broken before the patching is complete the repository will contain a mix of new and old files (what you call an invalid state). IcePatch2 will, however, continue the update where it left off the next time it is run.

Whether or not this is a problem with your environment depends on how you use IcePatch2. The way that our customers have traditionally used this in the past is that it is simply not possible to connect to the main server before fully patching so this was never an issue.