Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cocoon.apache.org
Received-SPF: pass (hermes.apache.org: local policy)
Message-ID: <20041012190937.43147.qmail@web53305.mail.yahoo.com>
Date: Tue, 12 Oct 2004 12:09:37 -0700 (PDT)
From: Paul Joseph <pjoseph_98@yahoo.com>
Subject: Re: the case of the over enthusiastic system admin ;-)
To: users@cocoon.apache.org
In-Reply-To: <416C166D.6060500@rosesareblue.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Good idea, I will do as suggested, thanks!

--- Russell Geraghty <russell@rosesareblue.co.uk>
wrote:

> There's nothing to stop you 'jar'ing the javascript
> and putting it on 
> the classpath, then use the resource:/ protocol to
> access the 
> javascript, this should prevent an enthusiast from
> noticing the javascript.
> 
> Russell
> 
> Paul Joseph wrote:
> > I am using cocoon to develop a webapp...all is
> going
> > well, but I am wondering - how does one guard
> against
> > an over enthsiastic system admin changing the
> > javascript files?  
> > 
> > The webapp is likely to be deployed on many sites
> and
> > one of them is bound to have an enthusiastic
> system
> > admin who may try to change things in the JS to
> get
> > them to work "his way." ;-)
> > 
> > What is the best way to prevent this from
> happening?
> > 
> > TIA
> > -Paul
> > 
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail:
> users-help@cocoon.apache.org
> > 
> > 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail:
> users-help@cocoon.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org