"Johnson, Kirk" wrote:
> The main thing to think about here is
> authentication: making sure people can access only their own data and nobody
> else's. Also, make sure everyone involved shares a clear idea of who bears
> responsibility for update mistakes. If the user has the ability to change
> their data, they have the ability to screw it up.
Only three people will ever get to do these updates, and I'm one of them.
> Make a clear oversight
> plan: how much reviewing of their changes you will do before the changes go
> live, etc.
Zip, none, no reviewing at all. At least, not from my part. They get to do
their own damned reviewing, and if they screw up, being that they're the
president and VP, they get to deal with the customer, not me. Not customer
service.
--
W | I haven't lost my mind; it's backed up on tape somewhere.
+--------------------------------------------------------------------
Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130
IT Director / SysAdmin / WebSmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6
http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A.
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
