Hi,<br><br><div><span class="gmail_quote">On 9/6/07, <b class="gmail_sendername">Benjamin Tolputt</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The primary reason I suggested having the beam files "compiled into" the<br>executable is that the game publishing industry is quite strict about<br>having copyright protection mechanisms embedded into the deployment. I
<br>am recommending Erlang as the "primary" development language rather than<br>just the "scripting" language (as this would make best use of Erlang's<br>superior concurrency) and, as such, being able to protect (if only
<br>marginally) the beam files that actually relate to how Erlang loads<br>modules, executes, etc (i.e. the kernel, stdlib, etc) is somoewhat of a<br>commercial (as opposed to "technical") necessity.<br></blockquote>
</div><br>Why would beam files more securely protected if packed in a zip archive as compared to unpacked in a directory?<br><br>There is already a mechanism to encrypt the debug_info data that might be included in the beam files. I suppose it would be relatively easy to do the same with the actual beam code and decrypt at load time.