long filepaths & names - potential headache?
Posted: Fri Jul 19, 2013 6:11 am
Hello friends,
My app is coming along great, I am writing file operation functions.
My plan was to use filenames and folder names to help me get information more quickly, and so I am using relevant ID numbers to name them. My ID numbers are UUIDs.
My concern is whether I can possibly run into problems with the length of my absolute paths being too long to complete file operations. So far my tests have been successful on windows, and everything works fine.
an example length is
"c:/Documents and Settings/My Documents/UMP Data/LU-73310424-5960-4460-8c53-b7d9a535af3e/syncfiles/SF-73310424-5960-4460-8c53-b7d9a535af3e.ump"
Thats only 143 characters. The minnimum limit is 255 right?
These files may also be present in a network environment, so the absolute paths might get even longer....
Should I go ahead? or do something different?
I'm creating standalones for windows, osx universal, linux.
Thanks a million.
My app is coming along great, I am writing file operation functions.
My plan was to use filenames and folder names to help me get information more quickly, and so I am using relevant ID numbers to name them. My ID numbers are UUIDs.
My concern is whether I can possibly run into problems with the length of my absolute paths being too long to complete file operations. So far my tests have been successful on windows, and everything works fine.
an example length is
"c:/Documents and Settings/My Documents/UMP Data/LU-73310424-5960-4460-8c53-b7d9a535af3e/syncfiles/SF-73310424-5960-4460-8c53-b7d9a535af3e.ump"
Thats only 143 characters. The minnimum limit is 255 right?
These files may also be present in a network environment, so the absolute paths might get even longer....
Should I go ahead? or do something different?
I'm creating standalones for windows, osx universal, linux.
Thanks a million.