An idea might be to follow the UI-model used by the "TiaIbGBak" components
found in IBOs AddOn directory. The good thing about this one is that it not
uses the Service API for us "Classic "Linux" and pre-6.0 servers" users -
still :-).

Looking for for a TIB_Services component, eventhough Ann thinks the Service
API is a "hack" - we hope for a better implementation in the future.

Doesn't some of the other RDMBS (MSSQL?) have a SQL interface for
backup/restore? e.g. BACKUP DATABASE MYDATABASE:GDB TO <some device> WITH
<options>.

Steffen Nyeland




"Geoff Worboys" <geoff@...> on 19-01-2001 03:33:19

Please respond to IBObjects@egroups.com

To: <IBObjects@egroups.com>
cc:

Subject: Re: [IBO] The Services API... again.

> It's just me or is there a contradiction in those two paragraphs?

Aside from my rather embarrassing typo...

> > "two complex"

My point I was trying to make (agree with) was; There is nothing
inherently wrong with additional components - where they are necessary
and appropriate. My initial look at the services API implies (to me)
that there is enough overlap if property requirements to make it so
that a single component is appropriate. The set of properties are
assigned to the component, and appropriate functions called to
initiate the service desired.

The interface would be relatively simple (I think) although, as you
suggest, the implementation would be rather more complicated. The
point being that there would be a lot of shared functionality, whether
you are doing a backup, restore or whatever. With this shared
functionality and common interface requirements, it seems to make
sense to present it in a single component.

For example: To take a backup and then restore to a new location...

with TIB_Services do begin
Database = <source database>
BackupFile = <destination>
DoBackup;
Database = <new database>
DoRestore;
DoValidate; // if you want.
end;

As I implied earlier; I could be wrong, but this has been my initial
impression.

Geoff Worboys
Telesis Computing