You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: