I agree that keel-container should just be a "container". However, I'm not
sure that all utilities are "applications" either. What about utility
"services", or "utility models"? Is there a need to differentiate types of
services? What's the difference between an application and a service, and
what is a utility? There might be common functions, such as Sequence, that
provide additional Keel component model options. I understand Shash's
reluctance to move that to an application, because it's not really an
application anyway. Perhaps, there's other packaging that's appropriate
for a model framework. It's important to keep the container minimal, so
this discussion is approrpriate.
+1
Doug Warren
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com