Changes between Version 73 and Version 74 of ippToPsps

Timestamp:

May 18, 2010, 1:23:05 PM (16 years ago)

Author:

rhenders

Comment:

--

ippToPsps

@@ -145 +145 @@
 Since {{{ippToPsps}}} will (soon) keep a record of all the jobs and corresponding exposure IDs in the IPP database, it is unnecessary for this information to be duplicated by the {{{DXLayer}}}, which currently has its own local database for this information.
 
-Rather than waste the code already written for the {{{DXLayer}}}, it can be used within {{{ippToPsps}}}, for example, the ODM polling scripts.
+The question remains of what should be done with the copies of the data currently retained by the {{{DXLayer}}}? The options are that it can either be deleted automatically after a defined amount of time, or the IPP can send list of batches it is safe to delete through the datastore, or perhaps the {{{DXLayer}}} should not retain files at all. Since it can quickly and easily acquire data from the IPP datastore anyway, it is probably unnecessary for it to hold any copies.
 
-The question remains of what should be done with the copies of the data currently retained by the {{{DXLayer}}}? The options are that it can either be deleted automatically after a defined amount of time, or the IPP can send list of batches it is safe to delete through the datastore, or perhaps the {{{DXLayer}}} should not retain files at all. Since it can quickly and easily acquire data from the IPP datastore anyway, it is probably unnecessary for it to hold any copies.
+This design would therefore mean simplifying a major PSPS component, the {{{DXLayer}}}, but rather than waste the code already written, it could be taken and used within {{{ippToPsps}}}, for example the ODM polling scripts. We would simply be shifting responsibility over from PSPS to IPP.
 
 === Advantages over previous design ===