> From: Leo Simons [mailto:[EMAIL PROTECTED]]
> 
> > Off topic but you've given me some great ideas about the 
> sort of thing 
> > we could talk about in the PMC.
> > 
> >   * case assesment of SOC infringments
> >   * policy to apply on IOC violations - community service
> >       or something stronger ?
> > 
> > ;-)
> 
> - I think this is technical (SOC/IOC are technical concepts), 
> hence the
> PMC shouldn't concern itself with it ;)

PMC is for social/political resolutions--we the developers are for
technical.


> - we do multi-dimensional separation of concerns. It is all but
> impossible to do it correctly in n dimensions, hence very difficult to
> assess in general

There is SOC which is good, and Fragmentation of Concerns which is
bad.  There is a certain threshold where there are too many concerns.
That has to be determined on a case by case basis.  Since I don't
have the context for your statement, I have no examples to offer you.


> - IOC violations sometimes really do make sense. example: A component
> requesting that the container shut down is violation of IOC, 
> but really
> darn handy as otherwise you'll have to run a separate JVM for the
> "container direction server".

I would never say this is ok.  What you are essentially doing is
stating that any Trojan component masquerading as a legit component
can shut down your system.  That is really bad.

All container management mechanisms have to be exposed by the container.
If your container exposes a "shutdown" service that states when the
container might want to shut down that is one thing.  However, there is
danger in that solution.  The container must always have the final say
on how and when to shut down.

Now, if there is only some way we can disable System.exit() from
components....

> - the PMC policy should be "do nothing". The _developers_ 
> however, they
> should frown for a bit and then try and explain why they thing the
> violation is a bad idea, perhaps supply a patch that fixes things.

Right.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to