Many thanks for the clarification! It's much appreciated.
We certainly have a no-decompile/r.e. clause in our contracts. And we trust our clients. But we don't trust some of their other vendors who are competitors in some areas and at times have access to the server. PerlApp makes it that much harder. I don't think it's paranoia.
Another reason for delivering an EXE is so the clients don't have to acquire and install Perl. In our market many many servers are run by people who wouldn't know how to do this or wouldn't want to.
Also it's easier for the clients if we deliver a single EXE than make sure each client is up to date on the 20 scripts that comprise the app.
So there are good arguments for almost anything!
Thanks again. Stephen
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
|
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.