*/
package jcifs.internal.smb2.nego;

import jcifs.Decodable;

/**
 * SMB2 Negotiate Context response data structure.
 *
 * This class represents negotiate contexts returned by the server
 * in response to negotiate context requests.
 *
 * @author mbechler
 */
public interface NegotiateContextResponse extends Decodable {

    /**

   *
   * ### Duplex Transmission
   *
   * With regular HTTP calls the request always completes sending before the response may begin
   * receiving. With duplex the request and response may be interleaved! That is, request body bytes
   * may be sent after response headers or body bytes have been received.
   *
   * Though any call may be initiated as a duplex call, only web servers that are specially

        Smb2CloseResponse response = request.createResponse(mockContext, request);

        assertNotNull(response);

        // Verify response has correct config
        Field configField = ServerMessageBlock2.class.getDeclaredField("config");
        configField.setAccessible(true);
        Configuration responseConfig = (Configuration) configField.get(response);
        assertEquals(mockConfig, responseConfig);

      override val nonDefaultValue: Authenticator = Authenticator { route, response -> response.request }

      override val badValue: Authenticator = Authenticator { route, response -> TODO() }

      override fun isDefaultValue(value: Authenticator): Boolean = value === Authenticator.NONE
    }

from your test's `tearDown()`.

### API

#### MockResponse

Mock responses default to an empty response body and a `200` status code.
You can set a custom body with a string, input stream or byte array. Also
add headers with a fluent builder API.

### Java
```java
MockResponse response = new MockResponse.Builder()
    .addHeader("Content-Type", "application/json; charset=utf-8")

Para eso, usa la `list` estándar de Python:

{* ../../docs_src/extra_models/tutorial004_py310.py hl[18] *}

## Response con `dict` arbitrario { #response-with-arbitrary-dict }

También puedes declarar un response usando un `dict` arbitrario plano, declarando solo el tipo de las claves y valores, sin usar un modelo Pydantic.

## 回應描述 { #response-description }

你可以用參數 `response_description` 指定回應的描述：

{* ../../docs_src/path_operation_configuration/tutorial005_py310.py hl[18] *}

/// info | 資訊

請注意，`response_description` 專指回應，而 `description` 則是針對整個「路徑操作」的一般描述。

///

/// check | 檢查

OpenAPI 規範要求每個「路徑操作」都必須有一個回應描述。

因此，如果你未提供，**FastAPI** 會自動產生 "Successful response"。

///

// error if the server message is invalid.  Calling Step after a conversation
// completes is also an error.
func (x *XDGSCRAMClient) Step(challenge string) (response string, err error) {
	response, err = x.ClientConversation.Step(challenge)
	return response, err
}

// Done returns true if the conversation is completed or has errored.
func (x *XDGSCRAMClient) Done() bool {
	return x.ClientConversation.Done()

<!--
    We used to set this only for packages that had manual supersource. That
    worked everywhere that I know of except for one place: when running the GWT
    util.concurrent tests under Guava.

    The problem is that GWT responds poorly to two .gwt.xml files in the same
    Java package; see
    https://groups.google.com/g/google-web-toolkit-contributors/c/CqYH59Dt_rQ/m/uVGW1QdUsXUJ
    for details.

	// Get object location.
	location := getObjectLocation(r, globalDomainNames, bucket, object)
	// Generate complete multipart response.
	response := generateCompleteMultipartUploadResponse(bucket, object, location, objInfo, r.Header)
	encodedSuccessResponse := encodeResponse(response)

	// Write success response.
	writeSuccessResponseXML(w, encodedSuccessResponse)

	// Notify object created event.
	evt := eventArgs{