As long as anyone else using those files in their code uses exactly
the same name, it will work.
Thanks James.
And I suppose, when running on a shared server, it doesnt hurt to reduce
the likelyhood of a conflict by using a more unique name like
FileChange3076 instead of FileChange
An easy
Paul's hash method works well for that too (and can potentially make
the lock name a little more manageable, depending on the length of the
file path). The double lock or something similar would be necessary,
since we are dealing with two files that need to be locked (the old
name and the new).
I
To be fair, it was Will who was getting confused! :-)
This e-mail is from Reed Exhibitions (Gateway House, 28 The Quadrant,
Richmond, Surrey, TW9 1DN, United Kingdom), a division of Reed Business,
Registered in England, Number 678540. It contains information which is
confidential and may
3 matches
Mail list logo