Bitcasa doesn’t throw up a warning flag on the play.
Once the file has been copied, there’s nothing to prevent the end-user from deleting the original. It’s not a problem that’s unique to Bitcasa, by any means. What is troubling, however, is the way Windows’ file copy system is leveraged to make it seem as though a file has been uploaded, even when it hasn’t been. That reality puts a damper on these sorts of services. I suspect this is a problem with NB itself, but this app needs a watchdog to play nice with others. I tried using a third-party tool to limit upload bandwidth, but NetBalancer wasn’t able to control Bitcasa’s speeds. Using Bitcasa to upload a file effectively shut off my ‘net for any other task. The bad news is that routers respond remarkably poorly to upload saturation, and mine is no exception. The good news is that upload speeds are excellent - my system was able to sustain a 100KB/s connection to Bitcasa, fully saturating my own upload bandwidth. This application sucks bandwidth like a fat kid on cake and it doesn’t like to share. That brings us to another problem - Bitcasa is an extraordinarily bad bandwidth citizen.
At 100KB/sec, it’ll take me nearly two days to upload these files. In reality, however, the file copy has barely begun.
Bitcasa for windows movie#
If I click on the movie from the I:\ location, it starts to play. There’s a file on my I:\, the file copy dialog has closed. The real problem here is that as far as the end-user can tell, the file copy is actually complete.
0 kommentar(er)
