Hi again Guac team: We have a solution for the download problem above - we have added a button that will initiate the download process for a specific folder (it is not initiated automatically when the user saves in that folder which was the problem above).
Now, our users keep complaining about the upload- despite ample documentation on the correct process of moving files (pesky users!). They upload a .mpp file and when they try to open it using MS Project they get the error described above. We are considering the following approach: When uploading, what if we watch if we can grab a handle on the uploaded file on the Unix side and if yes, this means the upload is complete and we can move it to a more MS Project friendly location (e.g Desktop). Thoughts? Thanks! ᐧ On Mon, Dec 12, 2016 at 1:14 PM, Mike Jumper <[email protected]> wrote: > On Mon, Dec 12, 2016 at 12:53 PM, Antony Awaida <[email protected]> > wrote: > >> Hi again Mike: >> >> What if we create a "staging" download folder and there is a script that >> checks the size the folder every X seconds. Once the size of the folder is >> stable, it moves the file to the actual Guac download folder? >> >> > And once that approach fails, will there be a staging folder for the > staging folder? Turtles all the way down? ;) > > You can try this, of course, but it is no more guaranteed to work than > what Guacamole is already doing, and it may actually make things worse: > > Your proposed heuristic assumes that a file is written continuously until > the application has finished saving the file, but this will not hold in > practice. What if the application writes the file slowly? What about > *extremely* slowly? The heuristic would incorrectly conclude that the file > is safe to download, automatically move the file to the download folder, > and effectively bypass Guacamole's own heuristics, ultimately resulting in > the download of a partial file. > > - Mike > > -- Antony Awaida CEO www.apporto.com
