<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 2/6/2013 1:31 PM, Doug Hellmann
wrote:<br>
</div>
<blockquote
cite="mid:CADb+p3Rh0KwpwfBPohkdbZeAN_EkDxJnh6+GQ3v2=f9djnZ1VA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div class="gmail_quote"><br>
<div><br>
</div>
<div>Entry points takes care of all of this. The code can live
anywhere, and each entry point gets a nice, short, unique name
to use in the configuration file. Developers can point to
anything they want, and non-developers don't have to know
class names. We all win.</div>
<div><br>
</div>
<div>Doug</div>
<br>
</div>
</blockquote>
<br>
Entry points are certainly more user friendly than raw classnames,
but they are still an intrusion of internal architecture<br>
into the user domain. It is still making the user think of
processing steps, rather than just objects to be stored.<br>
<br>
It may be sufficiently friendly that it is better than having two
layers of configuration, but better labeling of the pipes<br>
does not change the fact that you are asking the end user to
understand the plumbing.<br>
<br>
</body>
</html>