how much you like the client in first place.
Liability, on the other hand, is a legal issue - and unless you were
contracted to do this work then liable you are not. Even if the local IT
department doesn't actually host the site there's absolutely no reason for
backups to be neglected.
Jim Davis
_____
From: bret [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 4:17 PM
To: CF-Community
Subject: liability/guilt/blame question
So let say, hypothetically speaking of course, that you had a
sort-of-client from a former employer who wanted you to move their site
from the former employer's dedicated server to a shared hosting account
with the same hosting company that the dedicated server was at.
Now let's say this client handles their own DNS records.
So you move the files and database over, do some testing and send the
client an e-mail telling them to test the new site at the new IP address
(and if they get redirected to the domain name to let you know so you
can make sure they are testing against the new data), and once it looks
good, to contact their IT department and give them the new IP address to
point the site to. You supply the correct new IP address in that same
e-mail.
Let's say the client never contacts their IT department and they keep
using the DOMAIN NAME to update the OLD SITE on the OLD SERVER.
Now just for fun, let's say the former employer's server is shut down,
because, well, they went out of business a several months ago.
And just to spice it up a little, let's say the client's changes for the
last 3 months are gone. Kaput. Piped to /dev/null.
Is it your fault for not checking up on the client? Could you be held
liable for said lost data? Should you feel bad about it?
Keep in mind, you save all of your e-mail and have a record of having
told them to get the IP changed in their DNS records.
This is all, purely hypothetical, of course.
-Bret
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
