the case of the over enthusiastic system admin ;-)

[Paul Joseph <pj...@yahoo.com>]

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

Re: the case of the over enthusiastic system admin

[Paul Joseph <pj...@yahoo.com>]

Point taken, thank you!

(wasn't being arrogant though, just being prepared in
case ...atleast I think that was my motivation!)


--- Helma <h....@mi.unimaas.nl> wrote:

> > > > an over enthsiastic system admin changing the
> > > > javascript files?  
> > > > 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?
> 
> Hi,
> 
> I don't want to be rude here, but being a system
> admin (and developer) myself I
> tend to revolt against such arrogance. I think the
> best way to keep system
> admins from "tampering" your javascript files is by
> talking to them to figure
> out what _THEY_ would like.
> 
> I frequently ran into situations where we had to
> install software on numerous
> (100+) machines and the programmers required us to
> do something like doing each
> installation by hand and enter an individual license
> for each machine by hand.
> If they had taken the time to talk to system
> administrators who have to install
> and maintain the software they would have done it
> differently (which they
> finally did after much complaining from our side).
> 
> So: if you think they want to tamper with your
> files, why do you think they want
> to do that? In the end they want nothing more than
> you want: have the system
> running smoothly with as little effort as possible.
> 
> Bye, Helma
> 
> 
>
---------------------------------------------------------------------
> 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

Re: the case of the over enthusiastic system admin

[Helma <h....@mi.unimaas.nl>]

> > > an over enthsiastic system admin changing the
> > > javascript files?  
> > > 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?

Hi,

I don't want to be rude here, but being a system admin (and developer) myself I
tend to revolt against such arrogance. I think the best way to keep system
admins from "tampering" your javascript files is by talking to them to figure
out what _THEY_ would like.

I frequently ran into situations where we had to install software on numerous
(100+) machines and the programmers required us to do something like doing each
installation by hand and enter an individual license for each machine by hand.
If they had taken the time to talk to system administrators who have to install
and maintain the software they would have done it differently (which they
finally did after much complaining from our side).

So: if you think they want to tamper with your files, why do you think they want
to do that? In the end they want nothing more than you want: have the system
running smoothly with as little effort as possible.

Bye, Helma


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

Re: the case of the over enthusiastic system admin ;-)

[Paul Joseph <pj...@yahoo.com>]

Good idea, I will do as suggested, thanks!

--- Russell Geraghty <ru...@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

Re: the case of the over enthusiastic system admin ;-)

[Russell Geraghty <ru...@rosesareblue.co.uk>]

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