That is exactly an instance of which I speak.  The reference was correct but Poser chose the incorrect one.  That is for the developers to resolve - not merchants (in the final analysis).

I agree that it is rather easy to create at least seemingly unique filenames for geometry and texture files.  But remember 8.3.  When the number of files is in the billions and certain extensions are reused so often so as to be ridiculous (that is another topic for OS related gufaws) this seemingly good format failed.  Who'd ever need filenames with more than 11 characters?

Yeah, you get something like comb(11, 48) (48 = 26 alpha + 10 numeric + 12 other).  It's a very large number.  But not when the number of files reaches billions or trillions and there is no strict regulation on naming conventions.  The current filename length is 256 generally (iirc).  That allows for much larger combinations - and yet it is plain to see that filenames are continuously reused - even when long in attempts to be unique.  Let's face it - with autogeneration of files for various reasons, we can speculate on quadrillions or many factors more of files out there.  The number is just staggeringly impossible to imagine.
So that doesn't preclude the possible incidents of repetition.  Two merchants may use the same prefix (MyPoserStuff and MichaelsPoserShaders = MPS).  It has already been noted that 'unique' here can only be guaranteed by retaining a database of all files out there (in whatever context, this will be impossible) that people can use to identify uniqueness.

The internet uses a rather interesting system - fixed static IPs which are doled out to particular individuals while maintaining a layer of reusable 'local' IPs for internal networks (195. and so on) and dynamic IPs from a block of acquired static IPs.  That is the extent to which the internet avoids repetitive IP addresses (N.N.N.N where N >=0 <= 255).

Cinema 4D plugins have an ID system.  There is a block of LONG values for internal testing and use.  And there is a system to get unique IDs.  You request 'the next' ID from the pool for a new one.  You can always reuse one if not out there for a current product of your own.

You want truly unique filenames, you need a regulatory body to track and maintain that uniqueness.  There are no guarantees that obfuscated naming procedures (KDZ001FNK001A.obj) will never be reused otherwise.

C makes it easy to shoot yourself in the foot. C++ makes it harder, but when you do, you blow your whole leg off.

 -- Bjarne Stroustrup

Contact Me | Kuroyume's DevelopmentZone