Public Voice Network
- ATTN: Greedy Republicans 2626
- Beeeees! 1313
- Aging = Scary 1414
- Prometheus 145145
- Pic of the Day 6331563315
- The Pitch 114114
- Outfit of the Day 55
- the gif animation thread 1283912839
- Vid of the Day 1203512035
- FACE EATER 1616
- Pentagram: Forty Story 22
- Bilderberg 11
- alternatives to chrome?? 1111
- What are you listening to… 47024702
- Minimum rate? 33
- blog 5626556265
- Chick of the Day 1538315383
- Coda 2 3636
- Show your latest Pics 32953295
- News of the day... 138138
- Battlefield 3 305305
- New York 88
- Music over 5.1 System 66
- Random Fascinations? 55
Files on file server. 1111 Responses
Last post: 2 years, 2 months ago | Thread started: Mar 22, 10, 3:03 a.m.
Out of context: Response #5 [Mar 22, 10, 3:03 a.m.]
- airey
the idea of copying the files to your server and then copying back is regressive and decided around false logic.
if the server interupts you still have the file open so you can save locally, although this has happened once in 14 years for me.
if you copy the files off, you run multiple risks:
a: someone else can edit the file. meaning 2 or more edit a file then the last person to copy it back wipes any othe redits
b: the person working on the file forgets to copy it back (majority or fuck ups in anything is the people element) and you end up with an older copy on the server. which means an older version is backed up and if the person forgets or is away the next day and someone else goes to work on the file they're going to have the older version.

- View thread



