Opened 11 years ago
Closed 11 years ago
#8183 closed enhancement (wontfix)
Option to select request amount when upload data
Reported by: | naoliv | Owned by: | naoliv |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
In JOSM we have 3 advanced options to upload data:
- Upload data in one request
- Upload data in chunks of objects (where we can select the chunk size)
- Upload each object individually
We should also have an option to "Upload data in X requests", where X is a number that we can define.
(or redefine the first option to have always "1" as the default value, but with a textbox to increase it if wanted)
Attachments (0)
Change History (5)
comment:1 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:2 by , 11 years ago
And why not? :-)
Or: If it's not interesting that we have an 'upload data in X requests', then why do we have an 'upload data in chunks of X objetcs'?
I personally prefer to divide my objects in "number of requests" than "number of objects", specially when I am over a not-so-good Internet connection.
But to make it more generic, the 3 options that we have now could be simplified as only two options: "Upload in X number of requests" or "Upload in X chunks of objects"
Updating one and the other gets automatically updated too (if I increase the number of requests, than the number of objects get automatically decreased).
It would give us more simplified options while still giving all the flexibility that we would like to have.
comment:3 by , 11 years ago
Why not?: Because it needs time to implement. If you request something you need to explain why you want it.
But you still did not explain why a selection of number of chunks would be useful.
The chunk size is the main factor which defines upload time and thus smaller sizes may prevent data loss due to broken connection. I don't see a positive effect in your suggestion.
comment:4 by , 11 years ago
I know it takes time to implement and I know that it's low priority (that is why it's an enhancement request with priority "minor").
And I also gave a reason: simplify 3 options into 2.
If this is not a valid reason for a minor enhancement then I don't know what could be.
comment:5 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | needinfo → closed |
Sorry, you did not convince me. Reducing 3 to 2 can also be reached by dropping single upload, which is anyway only there for historic reasons. Defining the number of uploads does not solve any problem I can see.
Why?