Hi all, While dealing with file transfer in MSRP the following case happened to me and I wonder if anyone run into it before or had any thoughts to share.
Lets say we transfer file test.iso from Alice to Bob. Bob will acknowledge the reception of every chunk of data just fine. Since I/O operations usually take time to complete, we don't send the 200 to a SEND when actual bytes are written, but when the chunk is received over the network. While the file transfer is in progress the disk becomes full because some backup process kicked in and bytes can no longer be written to disk. Or, the hard drive is faulty and after assembling all the chunks together, the resulting hash differs from the original one. Either way, this fail transfer didn't end well even if all chunks were correctly sent and received over the wire. Is there any standard mechanism to overcome this situations? I couldn't find anything I could use on RFC 4975 nor RFC 5547. I guess something like a 'final status report' would do. Is there such a thing specified anywhere that I missed? Thanks in advance, -- /Saúl http://saghul.net | http://sipdoc.net _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
