Developing Perl against proprietary interfaces

sxmwb has asked for the wisdom of the Perl Monks concerning the following question:

I am wanting to start a project using Perl (first choice though I might have to consider Java) that would work with a radio scanner that has a proprietary memory format and would have to sign an NDA to get access. Further I would like to release my code as Open Source yet keep the memory format protected as required by the NDA and company. There are already several MS Windows solutions for this product but none for Linux or Mac.

Not sure if this is the best approach as I am just starting out and would like to give something back to the community. I have done several searches against perlmonks.org and other sites but have not come up with a definitive answer.

Any thoughts?

Thanks Mike

Comment on Developing Perl against proprietary interfaces

Replies are listed 'Best First'.
Re: Developing Perl against proprietary interfaces by samtregar (Abbot) on Apr 22, 2008 at 16:51 UTC
It seems like the way most people deal with this is to ship a compiled binary that interfaces with the secret code and a larger open-source library that talks to the binary blob. In your case the binary blob would probably be compiled C code that you interface with via XS or Inline::C. The goal should be to keep the C code as light as you can without exposing the secrets of the memory format. The alternative is to not sign the NDA and build the interface by reverse-engineering. You could load up the existing Windows implementations and watch what they do with a debugger. Then you can release your code under whatever license you want. (After you talk to a lawyer, of course.) -sam	[reply]
Re^2: Developing Perl against proprietary interfaces by wade (Pilgrim) on Apr 22, 2008 at 17:34 UTC
Instead of linking your C with Perl using raw XS, you might consider http://www.swig.org/. It builds the XS for you and, if you so choose, you can convert directly to Java. I've used SWIG before and it's really easy. -- Wade	[reply]
Re^3: Developing Perl against proprietary interfaces by samtregar (Abbot) on Apr 22, 2008 at 18:29 UTC
You might, but I wouldn't. I've also used SWIG and I found it to be mostly a waste of time. It offers something I don't need (bindings for multiple languages) in exchange for greatly increased complexity. That complexity hides the actual details of the XS interface that you'll need to effectively debug your code. And you will need to debug your code! -sam	[reply]
Re^4: Developing Perl against proprietary interfaces by wade (Pilgrim) on Apr 22, 2008 at 20:31 UTC
Re^5: Developing Perl against proprietary interfaces by wade (Pilgrim) on Apr 22, 2008 at 21:32 UTC
Some notes below your chosen depth have not been shown here
Re: Developing Perl against proprietary interfaces by locked_user sundialsvc4 (Abbot) on Apr 24, 2008 at 14:38 UTC
It might be possible for you to create a library as an object-code-only Perl extension, passing your requests for the actual memory-format through that cloak. I would carefully consult the NDA for more information, and discuss it with my attorney. (You do have an attorney, right? And you never quite beat him at golf, right?) Another possibility is to discuss your intentions with the company which owns the information. If the idea that you have might be profitable business (or good-will) for them, argue that point.
Re^2: Developing Perl against proprietary interfaces by sxmwb (Pilgrim) on Apr 25, 2008 at 00:11 UTC
I have not seen how to create a library as object-code-only Perl extension. I will take a look, if you have some direction that would be helpful. I have actually figured out 80% of the file format on my own. Not sure how that might impact me. If I move forward on the NDA I will make sure I have a lawyer look at it. I am not sure they are looking at what I plan as a profitable business venture I just want to provide access to tools for this radio scanner on OSs other then Windows. Also, it looks like fun and a challenge. Mike	[reply]
Re: Developing Perl against proprietary interfaces by Anonymous Monk on Apr 23, 2008 at 03:43 UTC
Proprietary codecs suck, and if they're asking for NDA, it must mean they don't have a patent, so they must be relying on DMCA, which may or may not affect you. Besides, once they release software, they've released the format.	[reply]
Re^2: Developing Perl against proprietary interfaces by samtregar (Abbot) on Apr 23, 2008 at 17:02 UTC
Um, what? Plenty of companies combine NDAs with patents - Nvidia and ATI come to mind immediately. It's the legal version of defense-in-depth. The DMCA probably only comes into play if you have to circumvent copy-protection to do your reverse-engineering. -sam	[reply]