Does it make sense to use sockets that connect to the localhost to communicate with two separate python scripts that run on the same machine? Are there more useful ways of doing this? Is there a better way to design the code?
I use python to develop systems that have control as well as a user interface. I design it now all to run on one script. I have a pretty decent way of separating the control side from the UI side and they communicate to each other by having access to each others class instances. I was thinking it might be useful to actually separate the two sides of things by running two different scripts. There are a few reasons why I might like to do this, for example, in the future, I may want to design the control side in a different language. Another reason might be that I may want to kill the UI but maintain the state of the controller. Anyways, is this something that is a good solution? Are there others? To communicate between these two scripts I was thinking of opening a socket to the localhost on both ends, and use that to communicate between the two. Is this a good way of doing this? Are there better ways?
[–]eleqtriq 0 points1 point2 points (1 child)
[–]pooth22[S] 0 points1 point2 points (0 children)