Idea: Sockets

[schickling]

What is the problem this feature would solve?

• requirements
  • stateful
  • bidirectional
  • multi-plexing
  • support "protocol schema" similar to RPC schemas
• use cases:
  • effect cluster (cc @mattiamanzati @IMax153)
  • chrome extensions
• further thoughts:
  • Idea by @mikearnaldi: could it make sense to allow for sockets with more than 1:1 communication

What is the feature you are proposing to solve the problem?

Some sort of Socket abstraction. TBD.

What alternatives have you considered?

No response

[IMax153]

There is some work already done on sockets in /platform FYI:

• https://effect-ts.github.io/effect/platform/Socket.ts.html

It's used to enable the functionality of the dev tools backend for the VSCode extension.

[mikearnaldi]

There is some work already done on sockets in /platform FYI:

• https://effect-ts.github.io/effect/platform/Socket.ts.html

It's used to enable the functionality of the dev tools backend for the VSCode extension.

Seems like this is lower level compared to what's discussed here, the discussed abstraction is more alike a bilateral rpc over a stateful channel, maybe Socket isn't the right name for the abstraction