rosyatrandom said...
Some questions:
- Why is the [element type][element id][ []=0& ] part repeated?
- The progress request doesn't differentiate between lesson and review elements, and is done for each set. Does that work on the basis that a element can only be in either the lesson OR review queue at any one time, so specification is unnecessary?
- If you have a large queue, might this run into the GET URL character limit?
1. the first one is the number of times you got the Meaning wrong, and the second is the number of times you got the Reading wrong, the double up doesn't seem to affect radicals, but I might change the script to make it a little more consistent.
a string like "/json/progress?k18[]=0&k18[]=2" tells the server that you got the meaning for 工 right first time, but got the reading wrong twice.
2. it doesn't differentiate but but the code is asynchronous, the part that submits the answers only runs after it knows which answers to submit, from the /review/queue? and the /lesson/queue? responses, which probably won't both come back at the same time.
I would say yes, it will only be in one of those queues so sending the appropriate code will affect the item accordingly. I wouldn't be surprised if it was all just one queue server side and served to the client according to the status of each item, but now I'm speculating.
3. You make a good point about the Get character limit, like I said, I'm not letting this command anywhere near my 2600 reviews so I might just have to look into it an split it programatically. It would still be untested and purely academic.