> > 2) More importantly, is it possible to prevent a customer from peeking
into
> > said database once it is deployed on their machine?
ROT13 it, then threaten them with the DMCA.
(Yes, that was a joke.)
steve
---(end of broadcast)---
TIP
On Fri, Aug 31, 2001 at 08:59:53AM -0400, Mike Arace wrote:
> 2 questions:
I'll let someone else handle the first one.
> 2) More importantly, is it possible to prevent a customer from peeking into
> said database once it is deployed on their machine? A large part of what
> makes my applicatio
On Fri, 31 Aug 2001, Mike Arace wrote:
> 1) Is it legal to bundle Postgresql with another commercial application,
> assuming the database will have to be significantly reconfigured and tuned?
> (at the application level, not the source code level) I read over the
> licenses I could find on th
On Fri, Aug 31, 2001 at 08:59:53AM -0400,
Mike Arace <[EMAIL PROTECTED]> wrote:
>
> 2) More importantly, is it possible to prevent a customer from peeking into
> said database once it is deployed on their machine? A large part of what
> makes my application proprietary is the data model in t
"Mike Arace" <[EMAIL PROTECTED]> writes:
> 1) Is it legal to bundle Postgresql with another commercial application,
> assuming the database will have to be significantly reconfigured and tuned?
> (at the application level, not the source code level) I read over the
> licenses I could find on
> 2) More importantly, is it possible to prevent a customer from peeking
into
> said database once it is deployed on their machine? A large part of what
> makes my application proprietary is the data model in the database, and
it'd
> be tough to maintain a competative edge when everyone can see e
Hi everyone,
I'm working on a (sorry) closed source application which consists of Java
servlets, beans, and client applications talking to a postgresql database.
Now, lets say I'm interested in bundling this all together and selling it to
customers.
2 questions:
1) Is it legal to bundle Pos
