OPENING MULTIPLE LOGOS INSTANCES (SESSIONS)

I don't ask for your opinion, nor do I ask you about you methods. So please don't ask me about mine.

If you can't offer a solution than its none of your business, just ignore my request.

Patrick, in order for us to provide the best answers rather than just an answer, we need to know what you are trying to achieve. Often this will lead us to recommend a more appropriate tool or an alternative way of considering the issue. We are just fellow users of the software who are trying to help others use the software in ways that meets their needs. We have to cooperate with one another if that is to happen.

I am looking for a solution to a clear limitation which I see with a program I have invested in.

Do you have any programming experience? If you do, you will know that synchronizing data across all instances of an application is a very thorny problem as you have no control over the speed of the communication between the instances of the application but must still determine which actions are applied in which order to keep all the instances synchronized and correct. It is standard practice to design this synchronization to capture time and data by user by device by application simultaneous despite multiple operating systems. You are asking that the synchronization be by session (task number) by user by device by application across multiple operating systems.  This adds the data I/O on a single machine as a variable ... how do you synchronize "mass updates" e.g. adding a tag to a group of resources in the library with individual requests e.g. adding a note? or a separate mass update. Even with only one instance running under a user id on a machine, this will occasionally fail in Logos as the second request assumed that the first request was completed when it was still in progress. At this time, the technology is such that to allow multiple instances would slow performance down significantly while incurring a significant development and maintenance cost. I would assume that technology will address the issues that make you want to have multiple instances running simultaneously on the same user account on a single machine. It you trust my crystal ball, I suspect it will be some form of virtual session in order to minimize the resources required for the storage and synchronization in the near term. For the long term I make no prediction.

All of which boils down to my admitting that were your request to be implemented, I would be rather aghast at the Faithlife prioritization of a feature that fails all reasonable cost analysis measures. That is not to say I don't recognize the appeal of the feature as I do at times run an instance of Logos and one of Verbum simultaneously on a single account on a single machine. I do so knowing where the pitfalls of doing so lie.

But this thread did make me wonder, why can you run Verbum (re-badged Logos) and Logos at the same time? Probably some reason.

You can and I do. The only "glitch" I know of is that the download status of a resource is (or was) at the device level.

proper virtualization / sandboxing would make this a complete non issue

You are correct that these are techniques that are used to handle/hide the issues; I was speaking at the physical/hardware level of what has to physically happen. Where I am having trouble figuring out how to help you is that I do not understand why you want a particular implementation that is costly to develop, increases resource requirements significantly, and slows performance. If you look at MSWord for example, you have multiple documents open in a single instance of the software. It is only in IDE's and server software that I have seen multiple instances of complex software running simultaneously. What is it about your process that makes you require multiple instances of the software? I can easily understand the need for multiple workspaces (i.e. with taskbar and command box) rather than simply multiple (floating) windows. Why isn't that a viable option for you?