Allow Custom Buffer Path via Agent Parameters #106
Description
Hello,
Currently, the buffer path is hardcoded in MTConnectAssetFileBuffer.cs, which limits flexibility in certain deployment scenarios. For example, in containerized environments, the buffer is lost upon container restart. It would be beneficial to allow customization of the buffer path, such as pointing it to a /persistent directory, to ensure data durability.
We’d greatly appreciate it if you could add support for specifying the buffer path through agent parameters. This would make the system more adaptable to various runtime environments.