我在寻求与一家小公司建立伙伴关系的过程。该公司正在寻找一种算法，可以提高他们的利润，我有一些原型软件，可以帮助他们。我的软件的核心是非常保密的，如果该公司得到一个抓住它，那么他们肯定不会需要我。我肯定会签署与他们的合同，我将有法律保障，但我还是希望把尽可能多的保护层他们和我的商业秘密成为可能的。

I'm in the process of exploring a partnership with a small company. The company is looking for an algorithm that can improve their profits and I have some prototype software that can help them. The core of my software is very confidential and if the company gets a hold of it, then they will certainly not need me. I'm definitely going to sign a contract with them and I will have legal protection, but I still want to put as many protective layers between them and my "trade secret" as possible.

我可能会用他们的开发工作接近自动执行我的算法，并在他们的系统集成，但我想提供一个DLL中的核心功能，所以我可以保护我的商业秘密，但仍然有能力与他们的开发工作。是混淆值得给予我的情况？是否有其他合理的选择？

I might have to work close with their developers to automate my algorithm and integrate it in their system, but I want to offer the core functionality in a DLL so I can protect my "trade secret", yet still have the ability to work with their developers. Is obfuscation worth it given my situation? Are there other reasonable alternatives?

推荐答案

我不知道这是一个选择，但是你可以考虑使用的 WCF 或 XML-RPC 或 REST 或什么的。

I don't know if this is an option for you, but you might consider providing the algorithm as a web service using WCF or Xml-rpc or REST or something.

当然，随着 HTTPS 。

这样，他们可以使用的算法，但他们永远无法得到你的code。

That way they can use the algorithm, but they can never get at your code.

如果只要算法不需要太多的往返或大量的数据被转移工作。这是说，只要该算法不需要使用实时与℃的响应; 100毫秒左右。

Should work as long as the algorithm doesn't require too many round trips or huge amounts of data being transfered. Which is to say, as long as the algorithm doesn't need to be used in real time with a responsiveness of < 100ms or so.