-
Notifications
You must be signed in to change notification settings - Fork 7
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.
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
As an HTTP client, I can push data to an HTM model in a RESTful way #9
Comments
Should also return an error if overwriting a timestep which has been already processed. Specify such semantic errors in this thread. |
@fergalbyrne See #12. |
@JonnoFTW I'm thinking maybe the POST body for this one containing the data should just be a CSV string instead of JSON. Would be simpler and lighter. What do you think? |
JSON makes sure that you don't get the field order messed up. The model doesn't know what order the fields are going to appear in and this will complicate making a model, so I'd probably suggest sticking with JSON, unless you want to encode them form data. |
👍 |
/models/<id>
: push data to model identified by<id>
If model does not exist, return 404. Success should return 200. Errors should return non-200 response status codes.
Depends on #5.
The text was updated successfully, but these errors were encountered: