>> Just a note: MySQL allows this, it allows you to define service name, >> port, >> a few configuration options etc. > > Could you describe what are instances good for generally?
Obviously for testing. ;) But also for small(er) companies that won't do a separate server for each product, but use different Firebird server versions for different products. As you know, updating to a new Firebird server -can- cause headaches. And there's the story with deploying Firebird "under the radar", as part of your own product and not wanting to modify existing Firebird installations or not wanting to be dependent on existing installations. This happens more often than you think. > In MySQL, perhaps, they are used to separate users and their databases > on shared >hosting. Firebird is not supposed to be used with shared hosting at all. Firebird 3, with its separate user database, will actually improve the chances for it being used on shared hosting. And if it is, service providers -will- want to use multiple instances, cause some people will require newer versions (eg version 4), while others will stay on v3. Why isn't Firebird supported to be used with shared hosting? With regards, Martijn Tonies Upscene Productions ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
