I've created a module that at first, was designed to be standalone. Since, I've updated it to make it network-capable, and it now, in one specific mode, acts as a distribution centre, commanding other systems to perform the tasks and return the results. The standard mode of single-system is still available
I've found that now I have to manage the results from the local instance a lot differently than the remote results, so I'm effectively doing a lot of duplicate work.
My options are: maintain the project and handle both the local results and the network results seamlessly, fork out the module and spin off a ::Standalone version that functions like the pre-network version, or assume by default that at minimum, localhost traffic will always work, and have the local procedures work over a network call to a localhost listener, even if the user doesn't want to ever use the distribution aspect of the dist.
What are your thoughts on this? Is it ok to assume at minimum local (ie. localhost) network comms in today's world, or would you take one of the other approaches (or even one I haven't considered)?
In reply to To assume network or not by stevieb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |