Python SDK design for Http.File when it appears in non-multipart request body and response body (DO NOT MERGE)

[Yuchao Yan (msyyc)]

No description provided.

[Johan Stenberg (ex-msft) (johanste)]

This loses both content type and suggested file name. And it is a very dangerous operation for large amounts of data.

[Yuchao Yan (msyyc)]

For

  @route("/base64")
  @scenario
  @scenarioDoc("""
    Test base64 encode for bytes body.
    Expected body:
    "dGVzdA==" (base64 encode of test, in JSON string)
    """)
  op base64(): {
    @header
    contentType: "application/json";

    @body
    @encode(BytesKnownEncoding.base64)
    value: bytes;
  };

Python SDK API will decode it with base64 like

autorest.python/packages/typespec-python/test/azure/generated/encode-bytes/encode/bytes/responsebody/aio/operations/_operations.py

Line 279 in 0c3981b

deserialized = _deserialize(bytes, response.json(), format="base64")

. But what if "content-type" is "application/json" but the response body is not encoded with base64 like this case: https://github.com/microsoft/typespec/blob/4d4afdabef3fed9b2d5f017a61e34286970bbff2/packages/http-specs/specs/type/file/main.tsp#L39-L47. Then typespec type bytes can't work and only Http.File could reprensent this scenario.

That's my understanding why we need Http.File as response body.