Re: Multiple Application Instances

FROM : Daniel Hazelbaker
DATE : Thu Apr 07 03:38:23 2005

That may be what I have to do, but as I said I had never expected to
do this, and even had decided against it as an option but now people
are requesting the ability to do so.  So I have a bunch of global
arrays that handle caching and other globals and references to globals
that I would have to replace and recode to be instance specific.  For
example, there are about 30 classes that reference a global pointer to
the "main server" instance a few dozen times each. Most of these
classes use class methods to load an object from the database and
re-link ID-pointers to other objects. So it is not an easy task to
convert this to be instance specific.  In retrospect I can see that was
probably not the best coding practice, but well.. here I am. :)

   However, from the responses I have gotten off-list as well it is
looking like there is no "decent" solution to this and I need to
rewrite the portions of code that are globalized and come up with a
optimized way to make them instance specific.

Daniel

On Apr 6, 2005, at 1:10 PM, j o a r wrote:

> I don't see why you would need separate processes for each db? Why not
> just have a separate configuration file per db (if you even need
> that), and then create some sort of db-server object per db (ie. per
> db config), probably running in separate threads in your app / tool.
>
> Perhaps you can think of it as something like a document based
> application (think TextEdit), but where your documents are your
> configuration files. I'm not certain that you should use the "Cocoa
> document based app" templates for this purpose, but the underlying
> design could probably be similar.
>
> j o a r