[tdwg-tapir] Hosting strategies
roger at tdwg.org
Fri May 11 09:19:06 CEST 2007
There is a requirement that all wrapper type applications (TAPIR,
DiGIR, BioCASe and others) have but that I don't think we address.
All instances need to have:
Either a database on a server in a DMZ or with an ISP with the
ability to export data from the production database to the public
database and then keep changes in the production database synchronize
with the public database.
Or the ability to provide a secured/restricted connection directly to
production database through the firewall.
Configuring the wrapper software against a database seems a smaller
problem than getting a handle on an up to date database to configure
Should we have a recommended strategy or best practice for overcoming
these problems? Do we have any figures on how they are overcome in
the existing BioCASe and DiGIR networks?
Many thanks for your thoughts,
More information about the tdwg-tag