annotate ext/json11/LICENSE.txt @ 186:52322dde68ea

Fix erroneous logic for handling step and block size in prior commit The earlier change had a logical misconception. If PluginStub is receiving the correct step and block size back from the configure call, the plugin on the server side must have already been successfully initialised, as the step and block size are only returned in a successful configure response. This means the test for a failed initialise and redo with the correct parameters must be done on the server side (in LoaderRequests) not the client. The client has a more complicated job, which is to notice that a *successful* configure had returned different framing parameters from those passed to the initialise call, and to pretend that it had actually failed until the host called again with the correct parameters. We definitely need tests for this!
author Chris Cannam <cannam@all-day-breakfast.com>
date Mon, 06 Feb 2017 16:44:33 +0000
parents bf8e3e7dd7de
children
rev   line source
cannam@150 1 Copyright (c) 2013 Dropbox, Inc.
cannam@150 2
cannam@150 3 Permission is hereby granted, free of charge, to any person obtaining a copy
cannam@150 4 of this software and associated documentation files (the "Software"), to deal
cannam@150 5 in the Software without restriction, including without limitation the rights
cannam@150 6 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
cannam@150 7 copies of the Software, and to permit persons to whom the Software is
cannam@150 8 furnished to do so, subject to the following conditions:
cannam@150 9
cannam@150 10 The above copyright notice and this permission notice shall be included in
cannam@150 11 all copies or substantial portions of the Software.
cannam@150 12
cannam@150 13 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
cannam@150 14 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
cannam@150 15 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
cannam@150 16 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
cannam@150 17 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
cannam@150 18 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
cannam@150 19 THE SOFTWARE.