Open Ristovski opened 2 years ago
I don't have any specific plan for this - in its current state it's good enough for my use and it isn't at the top of the priority list for further development.
I deliberately stayed away from a full custom protocol initially because it's a lot of complexity that wasn't core to what Vivarium needed and that I didn't think I could support well. I was thinking that perhaps an adequate intermediate solution would be a proper output data socket but with relatively little configurability compared to a full protocol. I haven't thought it through in much detail though.
this protocol here could be a good candidate to solve this problem, but it is still not ready
Given the future deprecation notice in: https://github.com/inclement/vivarium/blob/94b4d6a68f4f18f01d44fe8d4a4f837449759f1c/config/config.toml#L67-L71
what are the (if any) plans/ideas for implementing a better IPC mechanism?
Will Vivarium use a custom Wayland protocol for this ala River? This for example is how yambar is able to extract the current workspace info from River directly.