🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:

>Well, what EXACTLY are you trying to accomplish?

One ConsoleApp.exe (no DLLs). (I can wrap it with a message loop if
need be).
User starts multiple copies so they can switch to different
parts/functions quickly.
Multiple users on network.

User 4 on her Instance 3 wants to restore data from backup (my own
backup code).  All instances need to be out of all files for the
restore to work. (It complains if a file is open)  Instead of User 4
running to the other end of the building to shut down the app that
someone left open when they went to lunch, I would like Instance 3 to
put out a message (to everyone) that they need to close all files.
Perhaps several types of message (prepare to close files, close files
now, prepare to exit app, exit app now)  Also note that User 4
sometimes forgets that she has files open on her other instances.
Also, what usually ends up happening is the user goes to _every_
computer in the building and makes sure the program isn't running
anywhere. And they always miss one the first time through.

Same for Update. All instances need to exit so the exe can be
replaced.

These are all "occasional" messages. The vast majority of the time,
the app will just be listening "just in case".   I'm envisioning some
other uses too, which might bump up the messaging to 2 or 3 a day.

So, I don't think message reliability is much of an issue, as the code
already handles user non-compliance. If the instance misses the
request, then the old sneaker net method still works. Or, the app
could re-request on non-compliance (would work for dropped, not
blocked messages)..

These are Not critical messages. They would just make the user's life
smoother.