[Proposal] Never fail to launch app

[flaviotordini]

I recently encountered an issue that prevents application startup (#178). This made me think how disastrous this scenario is when a user encounters it.

I think a design goal, if it's not already the case, should be to never fail to launch an app instance. If something goes wrong it should launch anyway, even if it is a second instance.

What do you think?

[itay-grudev]

We support that through the secondary instance flag. In essence this allows both the primary and multiple secondary instances to co-exist at the same time and you can use the sendMessage() method. See here for full documentation.

[flaviotordini]

I think you misunderstood. I'm talking about never failing to launch because of an internal error of this library.

Basically the abortSafely method should be removed and the app should start anyway if anything goes wrong internally.

[itay-grudev]

That actually a good point.

[itay-grudev]

I'm working on a version 4 of the library that uses network negotiation via local sockets for single instance protection (as opposed to shared memory or lock files). It's supposed to be the version 4 of the library. I'll implement it there.

[dail8859]

Just to put in my two cents...

It would be detrimental if there were two instances of my application ever running at the same time since they would be overriding settings and interfering with one another.

So if the functionality was added, please make it optional.

[itay-grudev]

@dail8859 That goes without saying. It's just a matter of changing the default.