changed the universe:> > Of course, there's a lot more to it than this, especially if there's more > > than one database that needs to be replaced in this manner... > > > >Can you explain this more detailled? What are your concerns when there are more > >databases? > But if you plan to use the same 'upload-folder' to receive replacement db files > from all your clients...I think that would be bad organization anyway: one shop should reside in one folder or in one virtual host. > ...even a single > client can upload two or more files at the same time.Yeah, that would kill the system. I don't know a solution yet, just a workaround: if there is more than one file in the upload folder than delete them and change nothing. Just send the customer and the admin a mail Hell, what's going on? There were two files uploaded, we had to delete them all... > And if by chance two or more fo the newly-uploaded files have the same name, one > will probably overwrite the other, or else the second one will be given a > different name ... and that's another problem entirely.When a customer overwrites his own file, it is not my problem ;-) But that brings up another question: If any user can trigger the update by entering the shop it could happen that he comes in right at the same time when an upload is in progress but not finished and I believe that will corrupt the file. So it would be better to have the customer start the update manually via his web-interface. Even the situation with more than one uploaded file can be handled better - the customer gets the error message in the browser and knows immediately what is going on. > There's an issue dealing with that 'panic button' you might want to think about, > too. It's a good idea in gereral, but if the user uploads two files in > succession and they are both bad, and if he doesn't use the panic button in > between the uploads, then using the panic button will not replace a bad db file > with a good one, it will replace the bad one with another bad one ... :)Yes, I had this problem with an other database. And the problem with multiple uploads too. I switched to a more sophisticated solution: I allow multiple uploads but no automatic updates. The customer loads his files up and starts his web interface. There I list the files in the upload folder, the files in the backup folder and I have a panic button (all files have radios). Then he has to decide which uploaded file to use and - if he has a bad day - which backup to use. I know, this needs a customer who is willing to learn something. But people who want to administrate their own databases are usually people who understand technical requirements... Peter __________________________________________ Peter Ostry - po@ostry.com - www.ostry.com Ostry & Partner - Ostry Internet Solutions Auhofstrasse 29 A-1130 Vienna Austria fon ++43-1-8777454 fax ++43-1-8777454-21
Peter Ostry
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
ShipCost Data Base (1998)
RE: WebCat cannot handle compatible search parameters? (1997)
Tcp Connect and IPaddress (2000)
[WebDNA] Friday's.. WIP thread (2009)
[SHOWIF AND/OR] (1997)
Multiple prices (1997)
Virtual hosting and webcatNT (1997)
OT (2001)
WC1.6 to WC2 date formatting (1997)
First postarg not taking in $Commands (1997)
My solution... (1996)
using showpage and showcart commands (1996)
Protecting webdelivery (1997)
Announcement-WebCatalog 2.0 Released (1997)
File upload (2002)
PROBLEM (1997)
Simple Database close connection (2001)
SiteEdit NewFile.html ? (1997)
Adding content advice needed (1998)
WebCat2 several catalogs? (1997)