Hey Lewis, I am not sure that the PushPull is single-threaded - check out FileRetrievalSystem - which I believe is multi-threaded - maybe that¹s why?
CC @bfoster, can you help here? Cheers, Chris ------------------------ Chris Mattmann [email protected] -----Original Message----- From: Lewis John Mcgibbney <[email protected]> Reply-To: <[email protected]> Date: Friday, October 31, 2014 at 10:16 PM To: "[email protected]" <[email protected]> Subject: Multiple RemoteSpecs files in pushpull components >Hi Folks, >I am looking for some details on why we would require multiple RemoteSpecs >files within the pushpull component. >An example remote specs file can be found here [0] where essentially we >define individual pushpull client deamon's which do the heavily lifting >for >us in an automated manner. >The problem I am having here is that we reserve and initiate a LinkedList >data structure [1] for multiple RemoteSpecs.xml files and we then iterate >through this data structure [2] in an attempt to locate and process >configuration defined within each such file. >All of this is held in memory when we run one specific daemon as AFAIK the >pushpull component is a single threaded client. > >My questions are simple (and maybe trivial), do we require such a data >structure? Does anyone ever pass in multiple RemoteSpecs.xml files? > >Thank you >Lewis > >[0] >https://svn.apache.org/repos/asf/oodt/trunk/pushpull/src/main/resources/ex >amples/RemoteSpecsFiles/RemoteSpecs.xml >[1] >https://github.com/apache/oodt/blob/trunk/pushpull/src/main/java/org/apach >e/oodt/cas/pushpull/daemon/DaemonLauncher.java#L63 >[2] >https://github.com/apache/oodt/blob/trunk/pushpull/src/main/java/org/apach >e/oodt/cas/pushpull/daemon/DaemonLauncher.java#L102 > >-- >*Lewis*
