Lines Matching full:save
64 // save ID for for managing the status of the saving operation. So we
66 // unique save ID.
109 // Look up a SavePackage according to a save id.
145 // We manually start the save job.
154 // this kind of save job by ourself.
163 // A manager may have multiple save page job (SavePackage) in progress,
164 // so we just look up the save id and remove it from the tracking table.
165 // If the save id is -1, it means we just send a request to save, but the
172 // A save page job (SavePackage) can only have one manager,
212 // Cancel the request which has specific save id.
262 // in UI thread. In the latter case, the save ID will be -1, which means the
264 // thread, which will use the save URL to find corresponding request record and
382 // Generate a unique save id.
422 // so in here, we need not to do anything, just close the save file.
431 // Whatever the save file is renamed or not, just delete it.
451 // Close the save file before the copy operation.
