Currently, managing free areas when writing new data to files, is delegated to formats and components to solve. This somewhat hurts interoperability. This isn't needed when reading files, as allocating new areas is never required there, but it may be beneficial to have a 'standard' sub-section allocation table for avoiding collisions between components.
Currently, managing free areas when writing new data to files, is delegated to formats and components to solve. This somewhat hurts interoperability. This isn't needed when reading files, as allocating new areas is never required there, but it may be beneficial to have a 'standard' sub-section allocation table for avoiding collisions between components.