5 ms·
But how can you test if you protocol/document correct? Yes, Epycs code may have question about legit and some other stuff. But after it going to a beta or stabl
by skypeopensource 15y ago
But how can you test if you protocol/document correct?
Yes, Epycs code may have question about legit and some other stuff. But after it going to a beta or stable stage. We can use Epycs protocol documentation to write, for example, epycs.java and make it fully "clean room".
- cwzwarich 15y agoYou get someone who is not involved with the reverse engineering to test it.
- dredmorbius 15y agoLook up the term "Chinese Wall". What's required (for purposes of courtroom defense) is a clearly documented procedure in which those who have access to the source being reimplemented (the spec writers and testers) NOT be the coders, and vice versa. Another example is the SMB/CIFS reimplementation in the case of Samba. Here, because the protocol was an over-the-wire system, analyzing network packets (not covered by source analysis proscriptions) was sufficient to create a Free Software implementation.
- deleted 15y ago[deleted]
- skypeopensource 15y agoYeah, we will do it. But now project still at first stage.