i dont see why u need separation of backend/frontend... anyhow. i guesse u can make a frontend executable. On boot it checks if the backend is running or not. i

i dont see why u need separation of backend/frontend... anyhow. i guesse u can make a frontend executable. On boot it checks if the backend is running or not. if not. run it. Then establish a form of communication. usually sockets. if communication is needed 1 direction, just keep a read() open on the backend, if communication is needed 2 directions, u will have to keep a read() open on both ends. But again, separating front & backend for a desktop application, is kinda weird.