|
File I/O on Remote Server |
hyperscalper
|
Post subject: File I/O on Remote Server |
Post rating: 0
|
Posted: Mon 02 Sep, 2013, 16:40
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02 Posts: 656 Location: United States, Durham, NC
|
I am assuming that for your Remote Strategy Servers, that you may have more than just a single server available. Maybe a "farm" of servers, either now, or in the future.
If I restrict files to the root folder retrieved by IContext.getFilesDir(), then can I do File I/O on the Remote server from the Strategy?
I guess that "persistence" of a file on the Remote Server should not be assumed at all, once the Remote Execution instance terminates. Could you say a few words about that topic?
I was wondering whether we should anticipate file conflicts, with multiple Remote Strategies running since IContext.getFilesDir() could resolve to the same directory if on a single Remote Server machine or systems using a common filesystem?
Probably safest to anticipate possible file conflicts from multiple Remote Strategies, and code unique filenames to mitigate the issue of file conflicts.
Thanks for any tips, HyperScalper
|
|
|
|
|
API Support
|
Post subject: Re: File I/O on Remote Server |
Post rating: 0
|
Posted: Fri 20 Sep, 2013, 15:01
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17 Posts: 6139
|
IContext.getFilesDir for remote runs is unique per strategy, per session, meaning that other strategies are not able to access the directory and the same strategy won't be able to access it on subsequent runs.
|
|
|
|
|
|
Pages: [
1
]
|
|
|
|
|