This legacy web site is no longer updated but will remain online for the foreseeable future. UUhistle is not being actively supported or developed. Successor systems include Jsvee and Kelmu.
Using HTTP POST to Submit Solutions
UUhistle can submit learners' answers to exercises via HTTP POST to a server. This can be useful for grading or logging purposes.
For POSTing to work, the submit type setting must be set to POST either in the
course config file or, if using UUhistle in applet form,
in the applet parameters.
The server should respond with the text OK if successful. If UUhistle doesn't get this response,
it shows an error message to the user. If the server rejects the submission, it should respond with the text
ERROR. A more detailed error message (which will be shown to the user) can also be included using a vertical bar
like this: ERROR¦Incorrect user ID!
A POST request from UUhistle always contains the following parameters (key-value pairs). Some of them may have empty values when not applicable.
| Parameter | Explanation |
|---|---|
| course_id | A course identifier. See applet parameters. |
| exercise_id | An exercise identifier. Taken from the course config file, if one is used. |
| feedback | Written feedback from the user. (UUhistle prompts for feedback upon submission.) |
| max_points | Maximum points of this exercise. Taken from the course config file, if one is used. |
| points | User's points of this submission. Calculated by UUhistle. Grading schemes can be fine-tuned in the course config file. |
| sequence | A full list of the execution steps between loading and submitting. |
| system | Version information: UUhistle, Java runtime and OS. |
| total_time | Total time in seconds between loading and submitting the exercise. |
| user_id | A value that identifies the user (student). Taken from the applet parameters when available. When not, UUhistle prompts the user for an ID. |