Перейти к содержимому
Русский

PendingRemoteActorRef

Это содержимое пока не доступно на вашем языке.

Defined in: src/parallelism/PendingRemoteActorRef.ts:36

The ref system.spawn hands back for an actor that is being created on a worker (#1563).

spawn stays synchronous and the worker’s acknowledgment does not, so something has to be returned before the actor exists. Its identity is settled from the first instant — the path is chosen on the main thread, so path, equals and toString are what they will be forever — and only delivery waits: a tell before the acknowledgment is queued in order and replayed through the real remote ref the moment it arrives, so a caller that spawns and immediately sends sees exactly the ordering a local spawn gives. The queue is bounded across the whole extension, with the region buffer’s vocabulary for overflow: what does not fit goes to dead letters, never silently away. A spawn the worker refuses, or one that outlives its deadline, fails the ref the same way — everything queued becomes a dead letter naming this ref as the recipient, and everything after it too.

TMessage = unknown

new PendingRemoteActorRef<TMessage>(path, system, account): PendingRemoteActorRef<TMessage>

Defined in: src/parallelism/PendingRemoteActorRef.ts:42

ActorPath

ActorSystem

PendingBufferAccount

PendingRemoteActorRef<TMessage>

ActorRef.constructor

readonly path: ActorPath

Defined in: src/parallelism/PendingRemoteActorRef.ts:37

ActorRef.path

get isResolved(): boolean

Defined in: src/parallelism/PendingRemoteActorRef.ts:64

Whether delivery has switched to the worker’s actor.

boolean

ask<TResponse>(message, timeoutMs?): Promise<TResponse>

Defined in: src/ActorRef.ts:145

Request/response — send message and await the recipient’s reply. The framework synthesises a one-shot reply ref, injects it as both the sender slot and as message.replyTo, and resolves the returned promise with the first reply (or rejects with AskTimeoutError).

The caller never specifies replyTo on the message — the OmitReplyTo type subtracts it from the parameter type if the recipient declares it.

const value = await counter.ask<number>({ kind: 'get' });

timeoutMs must be a positive finite number; omit it (or pass undefined) to get ActorRef._defaultAskTimeoutMs — the configured actor-ts.actor.ask-timeout on a ref that can reach its ActorSystem, and DEFAULT_ASK_TIMEOUT_MS on one that cannot. 0, a negative value, NaN and Infinity throw OptionsError — see assertAskTimeout for why an ask has no “no deadline” mode.

TResponse = unknown

OmitReplyTo<TMessage>

number

Promise<TResponse>

ActorRef.ask


equals(other): boolean

Defined in: src/ActorRef.ts:241

ActorRef

boolean

ActorRef.equals


kill(): void

Defined in: src/ActorRef.ts:237

Kill this actor — raises ActorKilledError through the normal supervision path.

void

ActorRef.kill


send(message): void

Defined in: src/ActorRef.ts:125

Alias for tell — useful if you want to pipe something.

TMessage

void

ActorRef.send


stop(): void

Defined in: src/ActorRef.ts:234

Gracefully stop this actor after it drains its mailbox.

void

ActorRef.stop


tell(message, sender?): void

Defined in: src/parallelism/PendingRemoteActorRef.ts:51

Send a message to this actor. sender is surfaced as context.sender in the recipient.

TMessage

ActorRef<unknown> | null = null

void

ActorRef.tell


toString(): string

Defined in: src/parallelism/PendingRemoteActorRef.ts:93

The worker’s rendering once known — node-prefixed, like any remote ref — and the bare path until then.

string

ActorRef.toString