File sharing is the foundation of most all inter-computer communication that concerns the average user. Tasks such as browsing the Internet have downloading and uploading files, be they HTML pages or files to be downloaded and save, at their core. In home or office networks however the requirement is to enable users to access files in a way that rivals communally accessible filing cabinets. These methods can frequently fail, often more because of the files being shared than the methods themselves, so what conflicts arise when files are moved around?

Computer users with access to local networks will know the benefits of sharing folders among PCs, allowing their work to move with them across the network. Those without are forced to use USB drives to store their files while moving between all computers. This is a less than ideal solution when the computers are within spitting distance.

Sign up for the Tom’s UK newsletter to be in with a chance of winning one of two Sapphire graphics cards

One of the main roadblocks to sharing between operating systems in the past was the closed nature of the protocols used. Windows users could (with a very small amount of technical knowledge) share files easily between Windows machines, and users of other operating systems were similarly restricted to the protocols they used and no others. Over time these protocols have become obsolete, slowly reverse engineered to create open-source clients, or simply opened by their maker.

Much work has been done to create low-level protocols and systems to allow the sharing of files across local area networks. Many protocols have been modified to work on all operating systems, with some even being designed with cross compatibility in mind. The integration of remotely shared folders with file managers has always been a primary goal, allowing users to browse remote files as easily as their own documents.