I was looking at NAS solutions again today, as 1TB drives external get to my arbitrary but magic pricepoint of <$0.25/GB, and found this nice LaCie item.
What surprised me was buried in the comment by the second reviewer. He wrote:
"Also I had another USB external drive that I wanted to copy the data from to the NAS so I connected it directly to the NAS and mapped both drives on my laptop (which is wireless) to do a copy and it ran super slow, for some reason it did not just copy from drive to drive but it was transferring across my wireless."
Wow.
This is why we need basic computer "science" (really, a practicum that isn't focused on using apps) as a part of the general education. More English education needed to combat run-on sentences is also indicated in this case--but I digress.
Looking deeper into his situation and confusion, wouldn't it be cool to have devices smart enough to figure out what this user wanted (and expected) to do? I.e., the computer looks at the source and destination targets and sees that they're on the same IP and so hands them (maybe the source drive) a signal to check for routing optimizations, which might include looking for all USB hosts and clients for some matching target credential.
Or in this particular case, couldn't the NAS figure out what is going on, since it is receiving both the source and target destinations and spoof the client computer into thinking that the transfer is beginning, continuing and then ending as long as it takes to make the USB xfer? The user gets all the "flying folder" feedback (or spinning beachball for you Mac'ers) and for the appropriate time whilst the USB does its thing.
If Cisco and Comcast can spoof to interrupt Torrent copies, it can't be that hard to sniff this out. And for that matter, if the NAS kernel is Linux (as it surely is), couldn't you stuff some iptables rules that would handle this "feature"? Allowing this could be as easy as a feature in the web interface that, on detecting a USB drive, enables a checkbox that says, "allow disk-to-disk copies between by networked clients"? Defaulted to "on", of course. You might want the files to fly through your CPU/OS stack, because you might have antivirus checks to apply, Google desktop, or other benevolent (or, yes, malevolent) spyware to apply. Hmm... off by default then?
Surely I'm not the first to have thought of this (sm).
This is why we need basic computer "science" (really, a practicum that isn't focused on using apps) as a part of the general education. More English education needed to combat run-on sentences is also indicated in this case--but I digress.
Looking deeper into his situation and confusion, wouldn't it be cool to have devices smart enough to figure out what this user wanted (and expected) to do? I.e., the computer looks at the source and destination targets and sees that they're on the same IP and so hands them (maybe the source drive) a signal to check for routing optimizations, which might include looking for all USB hosts and clients for some matching target credential.
Or in this particular case, couldn't the NAS figure out what is going on, since it is receiving both the source and target destinations and spoof the client computer into thinking that the transfer is beginning, continuing and then ending as long as it takes to make the USB xfer? The user gets all the "flying folder" feedback (or spinning beachball for you Mac'ers) and for the appropriate time whilst the USB does its thing.
If Cisco and Comcast can spoof to interrupt Torrent copies, it can't be that hard to sniff this out. And for that matter, if the NAS kernel is Linux (as it surely is), couldn't you stuff some iptables rules that would handle this "feature"? Allowing this could be as easy as a feature in the web interface that, on detecting a USB drive, enables a checkbox that says, "allow disk-to-disk copies between
Surely I'm not the first to have thought of this (sm).
Posts
No comments:
Post a Comment