scabooz wrote:
Yep. Deployment for UT usually involves all the traditional
IT roles, just in development mode. By the time the
application gets through its initial lifecycle phases, subsequent
lifecycle phases need to be more strict. The admin role
early in the lifecycle should be very lenient as you said. The
admin role after deployment into production should be very
strict. The runtime impl/model has no way of differentiating.
There is a desire to use the same the implementation code in
the runtime in all phases of the lifecycle, so it's usually best to be
lenient in the runtime, and let the hosting environment take care
of knowing when to be strict.
I got the impression that you might have thought we were
disagreeing, but we're in violent agreement I think. To net it
out, Tuscany should be lenient in the model classes (warnings)
which enables a hosting environment with more context to
react properly.
Dave
+1 we are in agreement :) not sure everybody on the list agrees though.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
