_If_ the requested operation does change database state at all (I think p4 fstat //... does not) and client communication is needed for completion, the whole transaction will surely be abandoned. I'm quite sure that if I Ctrl-C a "p4 sync" op on the client, the server is not able to push more files. There are two possibilities (did not check): 1: Server state for transmitted files is updated, state for files not transmitted stays "old rev" 2: Whole client state stays unchanged (that's what a real atomic transaction would do).

IMO, sync is not necessarily to be considered atomic, so I'd rather expect case 1. I'll check this when I have good reason to sync something large...

After all, this does not answer my question how to stop the server pushing megabytes of output through the client API if the client app decides it has seen enough. I could simply shut down the whole ClientApi, ClientUser and Error objects. But I think this is a bad idea because: - We're in the middle of an operation, so call stack and client state might be a serious issue. - I'm reusing the same ClientApi for the whole life of my shell app and I'd like to keep it this way.

"Wenn ich Visionen habe, gehe ich zum Arzt." - Helmut Schmidt