Password protecting a revMedia 4 stack - "Yer - But - No"

[Jan Schenkel]

What Bill means is that the end-product revlet that you upload to the web server, is protected as it is turned into a different file format - but nothing prevents you from either putting the original stack right next to the revlet  for download by interested people, or sharing it to someone else via email or other means.
It's just that the revlet is protected, which sounds like a good decision to me in these days of DRM and IP-protection.

Jan Schenkel
=====
Quartam Reports & PDF Library for Revolution
<http://www.quartam.com>

=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


--- On Mon, 8/24/09, David Bovill <david at architex.tv> wrote:

> From: David Bovill <david at architex.tv>
> Subject: Re: Password protecting a revMedia 4 stack - "Yer - But - No"
> To: "How to use Revolution" <use-revolution at lists.runrev.com>
> Date: Monday, August 24, 2009, 2:24 AM
> Hi Bill - what's the logic for this?
> On the face of it one of the great
> advantages of growing the user base is to increase the
> ability of the
> community to create publicly available libraries and not
> leaving this up to
> the central company (however well resourced). I'm guessing
> there must be a
> motivation for preventing the "free" users from creating
> content which can
> be used by customers that have paid for a license seems
> perverse? What am I
> missing here?
> 
> 2009/8/23 William Marriott <wjm at wjm.org>
> 
> > I'm missing something here.
> >
> > All revlets are in a "compiled" format that cannot be
> reverse-engineered
> > back to a stack, whether or not a password is applied.
> This is similar to
> > the .swf/.fla distinction.
> >
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage
> your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>