Process-level components

[emil14]

Nevalang component is essentially a "server" that has input and output ports and performs some computations internally. It's possible to imagine a real (process-level) server with such API. It could be web-sockets or something else.

It's possible to imagine a network of such processes that performs message passing at the level of the network. They could even be distributed across several machines and perform distributed computations.

Of course there are problems to solve. For example, what happens when one node goes down? But that's another story. This is just an idea overall.

It would be really nice to have a nevalang component as an entry point to the server. Same idea, different scale

[gedw99]

Prefer SEE over web sockets but it just me .

I used to use WS, but with sse you get http 1, 2and 3 and a crazy simple architecture.
Also browser ready and no connection management and low battery usage.

The call back is just a namespace so you only need a single SSE per server / client.
Mobile / desktop etc have golang SSE client servers packages too so it’s not just web.

—-

Look at the examples it’s pretty easy to see that a system like golang NATS can do the in process , out of process and out of server needs.

you would not change any code , because nats is not based on ip addresses etc, but topics , so its topology agnostic.

you would not even need to tell the Nerv lang where a process or server is. Just use topics like we using the internet domain system.

It would be very fast. It would also be loss tolerant because it routes around servers going down as it has build in load balancing .
MIT has built in security too

[gedw99]

https://github.com/starfederation/datastar is a golang htmx system that uses SSE only. It does this so that it's a real time flow system.

Try https://github.com/starfederation/datastar/tree/develop/examples/go/hello-world to see what I mean.