deno.worker

[unicomp21]

can I run nats.deno in a browser worker, under deno.worker ?

https://deno.land/manual/typescript/configuration

[aricart]

Haven't tried it but if you enable the Deno namespaces to work on the worker, my guess is yes.

[gedw99]

@unicomp21 This is exactly what i was planning too.

Did you have any luck running i in a browser worker ?

[gedw99]

@unicomp21 do you mean running like this ? https://deno.land/manual@v1.31.2/runtime/workers

[unicomp21]

I don't know the current state of things on the deno side, my current focus is on using esfx w/ webpack.

[aricart]

@unicomp21 and @gedw99 nats.deno doesn't run in a browser. But nats.ws does! - the API is exactly the same. As for running in a worker, I have not tried running nats.ws in a worker, but Deno most certainly does.

https://github.com/aricart/services_demo/blob/main/service-adm.ts#L204

[aricart]

Not sure why you would... We have nats.ws for exactly that reason..

[aricart]

With that said the question is whether you are doing multiple connections or processing in the workers.

[gedw99]

With that said the question is whether you are doing multiple connections or processing in the workers.

Not exactly sure what your mean ...

From NATS cli:
nats -s x.x.x.:port req echo.actor-a'{{ message paylaod }}'

Then any NATS worker ( running as a WASM service worker in a browser or WASI on some device) will get that message.

Then those NATS workers can respond back etc.

[aricart]

You can call connect() from a worker and effectively that is an independent connection parallelizing within the same process. In my apps I have used multiple workers each with its own connection.

[gedw99]

You can call connect() from a worker and effectively that is an independent connection parallelizing within the same process. In my apps I have used multiple workers each with its own connection.

Thanks - I will try it out .