Guidance on TxFileManager lifespan

Aug 6, 2014 at 6:02 PM
Edited Aug 6, 2014 at 6:02 PM
As far as I can tell, TxFileManager is cheap to create and the expected use is to create a new one each time you need it (per transaction).

Is that right?

Either way, you should update the documentation to say how you intend for it to be used and whether it's thread safe or not.

When I see types called XXXManager, a light goes off in my head that maybe it should stick around for the duration of the application and should be disposed properly, etc.

Thanks for this project!
Nov 4, 2014 at 4:35 PM
Oops sorry I didn't see this message.

You can create many instances of TxFileManager as needed. There's a bit of overhead (like creating instances of any small class) but not much. Yes it's thread-safe.