beamng / physfs Goto Github PK

We need to add file change notifications to be added to the core.

File system notification support (create/delete/modify). See the following examples:

How to use the class : https://github.com/BeamNG/Torque3D/blob/master/Engine/source/core/volume.h#L436
Windows implementation: https://github.com/BeamNG/Torque3D/blob/master/Engine/source/platformWin32/winVolume.cpp#L60

Using something very similar would help us a lot porting our existing code over.

Follow-up to #2: analyse the performance of the library and improve the implementation and maybe change the API to reflect some design decisions to enable the users to use it better.

Unittests for:

• checks for most high level API with example zip and windows FS
• error / integrity checks

Stresstests / performance tests for:

• read/write throughput rates for the different backends? How much 'worse' is the .zip vz the windows FS for example. With such we could also see if exchanging minizip with something else would improve the performance.
• threading tests: do the backends work reliably in multithreaded environments, is it safe to assume there are no mutexes in place and that the code will not deadlock / hang?