What I mean by this is the Filr client sits in front of the existing network providers and has a mechanism to understand when it is on the corporate lan or not. So when on the corporate lan it would use NCP or CIFS and not proxy through Filr to access the data. This would require the Filr metadata to be kept in sync and other rest calls would need to be made but would have the added advantage that it would not require to go through FAMT and make normal NCP/CIFS calls inside the firewall. This should drastically improve Filr performance and load for internal users.
If remote it would revert to the normal Filr behaviour and use FAMT to access files. The functionality of the client should remain the same, just the transport layer changing depending on the user being on the corporate lan or not.
by: David S. | over a year ago | Desktop Client
Comments
This has been talked about in the past and would be a welcome enhancement. I was sure there was a IDEA for this already but I cannot find it, so this has my vote:)
This IDEA would not only benefit your suggested scenario but also would work well for environments leveraging VDI/TerminalServer and desktops with roaming users (no local caching of files needed here, just the Filr agent/explorer plugin servicing file sharing/comments etc on network files known by Filr).