Mark J. Nelson wrote: > - RTIs that may not be visible outside of Sun must use webrti. > > - RTIs that may be visible outside of Sun must use openrti. >
> - The choice of webrti vs openrti should be deterministic, per RTI. > > - RTIs for patch releases will continue to use webrti internally. > > - The internal and external (webrti and openrti) tools will share as > much common code and user interface as is practical. In this scheme, it appears that some subset of RTI data will live outside the firewall, and some subset will live inside the firewall, correct? The gate hooks which check the RTI before allowing a putback to complete will be running outside the firewall, once the gate migrates. There is no mechanism by which they will be able to access the SWAN-side RTI system. WebRTI also requires access to bug data, and the same issue exists there as well. There are other issues with a 'split brain' approach, such as what happens if an RTI is incorrectly classified and needs to move. In general, I don't believe that this sort of inside/outside approach is practical, the same goes for bug management. I think we need to stop trying to find technical fixes for something that is fundamentally an organisational and managerial problem. I believe the correct approach is to identify all these sorts of issues, and then ask for input and guidance from our management chain. -- Alan Burlison --
