Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deal intelligently with job numbers #37

Open
GoogleCodeExporter opened this issue Mar 20, 2015 · 1 comment
Open

Deal intelligently with job numbers #37

GoogleCodeExporter opened this issue Mar 20, 2015 · 1 comment
Labels
auto-migrated Priority-Medium Type-Defect

Comments

@GoogleCodeExporter
Copy link 

Ideal solution:

On startup, check active-hits folder to find the next unused job number.  Upon 
loading a new document, re-number the N jobs to be the next N available job 
numbers locally.

Original issue reported on code.google.com by [email protected] on 27 Aug 2010 at 9:39
@GoogleCodeExporter
Copy link
Author 

There must be a canonical solution for this kind of problem -- it would be an 
issue also if you get emailed a document with much higher job numbers than are 
in your directory, or worse, a document with the same job numbers as are in 
your directory.

Original comment by [email protected] on 27 Aug 2010 at 10:22

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Priority-Medium Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter