Re: hiding source from view from customer -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: hiding source from view from customer
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 27 Feb 2020 09:27:16 -0600
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@lists.midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.lists.midrange.com>
List-post: <mailto:midrange-l@lists.midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@lists.midrange.com?subject=unsubscribe>

On 2/27/20 9:04 AM, Jay Vaughn wrote:

so i know you can encrypt source from being debugged on on object...

but what if a source member is required to be shipped to the customer BUT
it contains proprietary code? How can it be protected from view?

Maybe put the proprietary code in an isolated module and not embed the source for that specific module?

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: hiding source from view from customer , Rob Berendt

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.