It seems to me that this is not really a Tapestry issue. I can see two
ways - there may be lots more.
A lot depends on exactly who the users are, how often they take backups,
their technical competence and the size of the backups.
Suggestions:
1. Ensure that your application writes the file to a well known location
on your server using some kind of unique file name. Provide a tapestry
service which streams the file to the user if they access a specific URL
passing an identifier which you can associate with the backup file. This
service would be pretty similar to the kind of service used to download
images/audio. Depending upon the size of the database you might need to
have two separate steps - one to generate the file and notify the user
it is ready and the other for them to download the finished product. It
may be worth zipping it unless you are using the postgres cdb format.
2. Create a 'backup user' for each database and let them connect
directly to the database using one of the many free open source tools
for postgres and take their backups that way using the pretty
sophisticated access control mechanisms in PG to make sure that users
only get data they are entitled to.
Hope that helps
Alan Chaney
Peter Dawn wrote:
guys,
i am using tap3. i am using postgres as my backend.
now my web app can be accessed remotely by users, who can then perform
certain functions like postgres database backup and restore.
now my problem is that when the database backup is performed using
pg_dump, the file is dumped on the local server. how can i let
somebody access this function remotely, tap executes pg_dump on the
server, and then dumps the file on the remote users computer and not
the local server. for pg_dump, i am executing the pg_dump on the local
servers command line, but from within tap.
any ideas how i can get this to work. thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
