Smaller front-end listeners

[2350568089]

Is your feature request related to a problem? Please describe.

I need a lighter, faster notification model。

Describe the solution you'd like

I am working on high-speed local computing applications that require pseudo real time display of results on the frontend. Using broadcast mechanisms to notify the frontend is clearly wasteful. Perhaps a linked list model can be added to the front-end, where the front-end always retrieves data from the head and the back-end always adds data at the tail. This linked list is only bound by one front-end method and can be bound by multiple back-end methods, and the back-end always comes with asynchronous operations and read-write locks.

Describe alternatives you've considered

i was use the electron to make a applications for hight-speed compute，the JavaScript is to slow for me, so now i want refactoring it to support scientist for our compeny.

Additional context

No response

[symball]

A simple way to achieve what you want is to implement nats within your Go app (it's very easy to embed within Go applications) and have the frontend use the NATS.js library to subscribe to topics.

[Robert-M-Muench]

So, a NATS server can be embedded into a Go program, or do you mean the client and a NATS sever is still needed?