Api vor Daemon Processes in Extensions

[schromp]

I stumbled upon the requirement for a daemon process in 2 extensions i wanted to write now.

What i propose:
a part of the vicinae api which you can pass a extension or object which is long lived and you have access to on later command invocations.

ill give a example of how i would use it:
i wanted to implement a discord rpc extension. however for the status to be persistant the connection the socket needs to stay open.
there is a rpc object in the library i use. If i could pass that to vicinae to keep it alive and retrieve it later i could use the connection further.

Im not sure on the implementation details, including if its possible how i image it, though

[aurelleb]

it would be great if you could write a snippet of code showing how you would like this to work exactly, so that I can picture this better. Not the RPC part but like how to initialize/deal with the long running thing.

[aurelleb]

this is very quickly turning into the Vicinae operating system 🤣

[schromp]

yeah that sounds good to me aswell. maybe having a daemon file makes it more clear what is running all the time aswell so thats a positive

and if that is out of scope for this application i would be fine with that aswell.
it would just add some convenience to the user because they wouldnt have to start a seperate process manually beforehand

[aurelleb]

I think it's great as long as we keep control over the running processes. Having an extension spawn stuff on its own is very error prone and can yield unexpected side effects

[schromp]

Maybe the user should also get a prompt to tell them that a daemon process is first run the first time.

Or maybe not because if you run the extension then you trust it either way so it doesnt really make a difference

[aurelleb]

yeah could be part of a future permission system I guess.