Hi, Overall I'm ok with this too but I shared the sentiment that Allen expressed:
I also wonder if the use of the idea that this fault is associated with instantiating the transfer protocol is correct. Is it the case that the error will always manifest itself when the DTI attempts to instantiate the transfer protocol? Are there cases where the error will only be detected when an attempt is made to move the first set of bytes?
Although, I can't think of specific use case my concern would be if there were some systematic effect that caused a transfer to terminate at some point during its transmission and repeated usage of the same protocol might lead to the same failure - do we already cater for this? else it might be good to promote the proposed fault to be more generic (possibly change the name TransferProtocolNotInstantiatableFault too) otherwise I'm fine ... Mario +-----------------------------------------------------------------------+ |Mario Antonioletti:EPCC,JCMB,The King's Buildings,Edinburgh EH9 3JZ. | |Tel:0131 650 5141|mario@epcc.ed.ac.uk|http://www.epcc.ed.ac.uk/~mario/ | +-----------------------------------------------------------------------+