[
https://issues.apache.org/jira/browse/GUACAMOLE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311478#comment-16311478
]
Nick Couchman commented on GUACAMOLE-473:
-----------------------------------------
{quote}
...but magically and silently renaming the uploaded file seems to me to violate
the principle of least surprise.
{quote}
I vote for a "Guacamole Surprise Edition" release, that violates this principal
at every possible turn! :-)
{quote}
That is what Windows normally do. It is a normal behavior of windows when
we download any file. Overwriting the existing file is something users
don't want.
{quote}
Google Chrome and maybe Firefox behave this way - adding a (1), (2), etc. to
files that are duplicates, and IE/Edge may even do this, but I do not believe
that Windows, in general behaves this way. Windows, if I recall correctly,
asks you what you want to do, and, further, has mechanisms for dealing with
situations where large numbers of files violate a constraint (like duplication,
read-onlyness, etc.).
I fully agree with you that silently overwriting the file probably needs to be
addresses, but I don't think that automatically/silently renaming, adding "
Copy of" or "(1)", etc., is the right way to go. That might be an option
during the prompt, like Windows provides, but it shouldn't be the automatic
behavior.
> Automatically rename uploaded file if destination file already exists
> ---------------------------------------------------------------------
>
> Key: GUACAMOLE-473
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-473
> Project: Guacamole
> Issue Type: Wish
> Components: RDP
> Reporter: Amarjeet Singh
> Priority: Trivial
>
> While uploading file which already exists in the shared drive it doesn't
> include 1 or 2 in suffix instead it overwrite the existing file in the shared
> drive.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
