I realize that the spec is clear on this subject, but I do not see that 'fixing' this issue would actually break the intention of the spec. It does however introduce the need in both win and linux client to be able to download and handle files with same name and path at the download location. Preferably by allowing the client to auto rename files to solve name conflicts (this would at the same time solve issues with incompatible file names between os:es and/or code-pages).
When the issue of virtual folders were introduced the possible name conflicts issue where discussed and the proposed solution there was quite simple, as long as the files have different TTH, show and share them both, if they have same name and TTH, choose one and show/share that file. I don't see why the issue covered by this bug report could not be handled similarly?
I realize that the spec is clear on this subject, but I do not see that 'fixing' this issue would actually break the intention of the spec. It does however introduce the need in both win and linux client to be able to download and handle files with same name and path at the download location. Preferably by allowing the client to auto rename files to solve name conflicts (this would at the same time solve issues with incompatible file names between os:es and/or code-pages).
When the issue of virtual folders were introduced the possible name conflicts issue where discussed and the proposed solution there was quite simple, as long as the files have different TTH, show and share them both, if they have same name and TTH, choose one and show/share that file. I don't see why the issue covered by this bug report could not be handled similarly?
1d