/// <summary>
/// Adds a new party to the set managed by the backing participant.
/// Caller specifies a party identifier suggestion, the actual identifier
/// allocated might be different and is implementation specific.
/// This call may:
/// - Succeed, in which case the actual allocated identifier is visible in
/// the response.
/// - Respond with UNIMPLEMENTED if synchronous party allocation is not
/// supported by the backing participant.
/// - Respond with INVALID_ARGUMENT if the provided hint and/or display name
/// is invalid on the given ledger (see below).
/// daml-on-sql: suggestion's uniqueness is checked and call rejected if the
/// identifier is already present
/// daml-on-kv-ledger: suggestion's uniqueness is checked by the validators in
/// the consensus layer and call rejected if the identifier is already present.
/// canton: completely different globally unique identifier is allocated.
/// Behind the scenes calls to an internal protocol are made. As that protocol
/// is richer than the the surface protocol, the arguments take implicit values
/// </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.DigitalAsset.Ledger.Api.V1.Admin.AllocatePartyResponse> AllocatePartyAsync(global::Com.DigitalAsset.Ledger.Api.V1.Admin.AllocatePartyRequest request, grpc::Metadata headers = null, global::System.DateTime?deadline = null, global::System.Threading.CancellationToken cancellationToken = default(global::System.Threading.CancellationToken))
{
return(AllocatePartyAsync(request, new grpc::CallOptions(headers, deadline, cancellationToken)));
}
/// <summary>
/// Adds a new party to the set managed by the backing participant.
/// Caller specifies a party identifier suggestion, the actual identifier
/// allocated might be different and is implementation specific.
/// This call may:
/// - Succeed, in which case the actual allocated identifier is visible in
/// the response.
/// - Respond with UNIMPLEMENTED if synchronous party allocation is not
/// supported by the backing participant.
/// - Respond with INVALID_ARGUMENT if the provided hint and/or display name
/// is invalid on the given ledger (see below).
/// daml-on-sql: suggestion's uniqueness is checked and call rejected if the
/// identifier is already present
/// daml-on-kv-ledger: suggestion's uniqueness is checked by the validators in
/// the consensus layer and call rejected if the identifier is already present.
/// canton: completely different globally unique identifier is allocated.
/// Behind the scenes calls to an internal protocol are made. As that protocol
/// is richer than the the surface protocol, the arguments take implicit values
/// </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.DigitalAsset.Ledger.Api.V1.Admin.AllocatePartyResponse> AllocatePartyAsync(global::Com.DigitalAsset.Ledger.Api.V1.Admin.AllocatePartyRequest request, grpc::CallOptions options)
{
return(CallInvoker.AsyncUnaryCall(__Method_AllocateParty, null, options, request));
}
/// <summary>
/// Adds a new party to the set managed by the backing participant.
/// Caller specifies a party identifier suggestion, the actual identifier
/// allocated might be different and is implementation specific.
/// This call may:
/// - Succeed, in which case the actual allocated identifier is visible in
/// the response.
/// - Respond with UNIMPLEMENTED if synchronous party allocation is not
/// supported by the backing participant.
/// - Respond with INVALID_ARGUMENT if the provided hint and/or display name
/// is invalid on the given ledger (see below).
/// daml-on-sql: suggestion's uniqueness is checked and call rejected if the
/// identifier is already present
/// daml-on-kv-ledger: suggestion's uniqueness is checked by the validators in
/// the consensus layer and call rejected if the identifier is already present.
/// canton: completely different globally unique identifier is allocated.
/// Behind the scenes calls to an internal protocol are made. As that protocol
/// is richer than the the surface protocol, the arguments take implicit values
/// </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.DigitalAsset.Ledger.Api.V1.Admin.AllocatePartyResponse> AllocateParty(global::Com.DigitalAsset.Ledger.Api.V1.Admin.AllocatePartyRequest request, grpc::ServerCallContext context)
{
throw new grpc::RpcException(new grpc::Status(grpc::StatusCode.Unimplemented, ""));
}
