When creating a new project pipeline, I'd like to have the possibility to create a folder that could be shared (i.e. with I/O rights) by all the services in a project. This folder could be used to save e.g. a library of code, some filed shared by all the services, or also where I?O files created by the services but NOT shared between different services can be stored and accessed. This folder would not be therefore following synchronization rules between services.
Expected behaviour
The user creates temporary files only in this shared folder, and shares with other services through the usual I/O mechanisms only specific output data. The different shared folders, instead, could be input and output only (e.g. with privileges) or without.
Actual behaviour
I/O folders within services are slow because of the synchronization issues, and may store redundant data.
User cases:
A library of pre-calculated fields can be located in a shared folder and there accessed by all the services simultaneously.
Customer libraries could be deposited ther
3.Intermediate Sim4Life projects could be saved/created there, and only after completing the job, saved & zipped to the specific server's output folder
Note: your environment was attached but will not be displayed
Long story short
When creating a new project pipeline, I'd like to have the possibility to create a folder that could be shared (i.e. with I/O rights) by all the services in a project. This folder could be used to save e.g. a library of code, some filed shared by all the services, or also where I?O files created by the services but NOT shared between different services can be stored and accessed. This folder would not be therefore following synchronization rules between services.
Expected behaviour
The user creates temporary files only in this shared folder, and shares with other services through the usual I/O mechanisms only specific output data. The different shared folders, instead, could be input and output only (e.g. with privileges) or without.
Actual behaviour
I/O folders within services are slow because of the synchronization issues, and may store redundant data.
User cases:
Note: your environment was attached but will not be displayed