Description of changes:
There were a few relevant breaking changes from MMS v1.0.4 --> v1.0.5:
Context.request_processor used to be a single RequestProcessor object (v1.0.4 code), but is now a list of them (v1.0.5 code)
the request headers stored in a given RequestProcessor object now correspond to a single request (makes sense given the above change), so RequestProcessor.get_request_property returns back a single value from the headers for a key rather than a single set of headers for a request ID
Context.set_response_content_type now takes an index instead of a request ID (v1.0.4 code, v1.0.5 code)
Testing done:
ran tox locally
rebuilt the MXNet serving image for CPU + Python 3 and ran local integ tests.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Description of changes: There were a few relevant breaking changes from MMS v1.0.4 --> v1.0.5:
Context.request_processor
used to be a singleRequestProcessor
object (v1.0.4 code), but is now a list of them (v1.0.5 code)RequestProcessor
object now correspond to a single request (makes sense given the above change), soRequestProcessor.get_request_property
returns back a single value from the headers for a key rather than a single set of headers for a request IDContext.set_response_content_type
now takes an index instead of a request ID (v1.0.4 code, v1.0.5 code)Testing done:
tox
locallyBy submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.