/// <summary>
/// Upload a DAR file to the backing participant.
/// Depending on the ledger implementation this might also make the package
/// available on the whole ledger. This call might not be supported by some
/// ledger implementations. Canton could be an example, where uploading a DAR
/// is not sufficient to render it usable, it must be activated first.
/// This call may:
/// - Succeed, if the package was successfully uploaded, or if the same package
/// was already uploaded before.
/// - Respond with a gRPC error
/// Errors:
/// - ``UNAUTHENTICATED``: if the request does not include a valid access token
/// - ``PERMISSION_DENIED``: if the claims in the token are insufficient to perform a given operation
/// - ``UNIMPLEMENTED``: if DAR package uploading is not supported by the backing participant
/// - ``INVALID_ARGUMENT``: if the DAR file is too big or malformed. The maximum supported size is implementation specific.
/// </summary>
/// <param name="request">The request to send to the server.</param>
/// <param name="headers">The initial metadata to send with the call. This parameter is optional.</param>
/// <param name="deadline">An optional deadline for the call. The call will be cancelled if deadline is hit.</param>
/// <param name="cancellationToken">An optional token for canceling the call.</param>
/// <returns>The call object.</returns>
public virtual grpc::AsyncUnaryCall <global::Com.Daml.Ledger.Api.V1.Admin.UploadDarFileResponse> UploadDarFileAsync(global::Com.Daml.Ledger.Api.V1.Admin.UploadDarFileRequest request, grpc::Metadata headers = null, global::System.DateTime?deadline = null, global::System.Threading.CancellationToken cancellationToken = default(global::System.Threading.CancellationToken))
{
return(UploadDarFileAsync(request, new grpc::CallOptions(headers, deadline, cancellationToken)));
}
/// <summary>
/// Upload a DAR file to the backing participant.
/// Depending on the ledger implementation this might also make the package
/// available on the whole ledger. This call might not be supported by some
/// ledger implementations. Canton could be an example, where uploading a DAR
/// is not sufficient to render it usable, it must be activated first.
/// This call may:
/// - Succeed, if the package was successfully uploaded, or if the same package
/// was already uploaded before.
/// - Respond with a gRPC error
/// Errors:
/// - ``UNAUTHENTICATED``: if the request does not include a valid access token
/// - ``PERMISSION_DENIED``: if the claims in the token are insufficient to perform a given operation
/// - ``UNIMPLEMENTED``: if DAR package uploading is not supported by the backing participant
/// - ``INVALID_ARGUMENT``: if the DAR file is too big or malformed. The maximum supported size is implementation specific.
/// </summary>
/// <param name="request">The request to send to the server.</param>
/// <param name="options">The options for the call.</param>
/// <returns>The call object.</returns>
public virtual grpc::AsyncUnaryCall <global::Com.Daml.Ledger.Api.V1.Admin.UploadDarFileResponse> UploadDarFileAsync(global::Com.Daml.Ledger.Api.V1.Admin.UploadDarFileRequest request, grpc::CallOptions options)
{
return(CallInvoker.AsyncUnaryCall(__Method_UploadDarFile, null, options, request));
}
/// <summary>
/// Upload a DAR file to the backing participant.
/// Depending on the ledger implementation this might also make the package
/// available on the whole ledger. This call might not be supported by some
/// ledger implementations. Canton could be an example, where uploading a DAR
/// is not sufficient to render it usable, it must be activated first.
/// This call may:
/// - Succeed, if the package was successfully uploaded, or if the same package
/// was already uploaded before.
/// - Respond with a gRPC error
/// Errors:
/// - ``UNAUTHENTICATED``: if the request does not include a valid access token
/// - ``PERMISSION_DENIED``: if the claims in the token are insufficient to perform a given operation
/// - ``UNIMPLEMENTED``: if DAR package uploading is not supported by the backing participant
/// - ``INVALID_ARGUMENT``: if the DAR file is too big or malformed. The maximum supported size is implementation specific.
/// </summary>
/// <param name="request">The request received from the client.</param>
/// <param name="context">The context of the server-side call handler being invoked.</param>
/// <returns>The response to send back to the client (wrapped by a task).</returns>
public virtual global::System.Threading.Tasks.Task <global::Com.Daml.Ledger.Api.V1.Admin.UploadDarFileResponse> UploadDarFile(global::Com.Daml.Ledger.Api.V1.Admin.UploadDarFileRequest request, grpc::ServerCallContext context)
{
throw new grpc::RpcException(new grpc::Status(grpc::StatusCode.Unimplemented, ""));
}
