The UrsaJ File Storage system would not have any sort of function without the robust operation of the integrated HFS Server.
This server is responsible for working with files on a given company's database. Every file which the HFS Server is responsible for working on is uniformly accessed through three HTTP File Storage components - (1) The ID, or in database terms, the primary key of the file; this is a unique identifier which distinguishes a file from every other file within the database. Then there's (2) The Information regarding the file; this consists of vital information describing the file - the actual space it takes up on the disk, the file name, the type of content within the file based on extensions, the date which it was uploaded into the server, and/or any dates which indicate when any changes were made to the file. These are only some of the pieces of information administrators have access to, for the security and integrity of the files being handled by the system. Finally, there 's (3) the data, or simply the actual file itself.
You'll notice that the file's attributes are placed in a field separate from the file itself; this is necessary, especially for people working on one file from two different locations within the office, just so that users could monitor any changes and when they were made. Furthermore, the system's naming conventions have made it possible for users to access certain files right away, provided they know the ID associated to the specific file.
Files are uploaded into the system through an upload form, generated by the system's related application. These forms are sent to the HFS Server URL by default. Depending on the number of files uploaded through one form, the HFS Server is able to determine the priority of which files to work on first. Any restrictions introduced by default or through an administrator are implemented during the upload process, and appropriate errors are reported just in case a certain file fails to meet requirements.
Files are consequently downloaded through and from the UrsaJ system through an application which generates a unique URL for the requested file, based on its ID component. Users are able to download the file by opening the URL. When the URL is accessed, this is when the HFS Server responds by returning the file and its data based on its ID.
You can say that this file storage system is simple, but it is really straightforward and efficient in handling the keeping and updating of files in a given company.