Anyways,I agree with noah: we define the terms and by doing so we define what it means. However, if you really want to avoid that ambiguity we could go for "unit of execution" - this does not at all imply that it's something that is doing the execution.
cheers felix On Mar 19, 2009, at 4:25 PM, David Zülke wrote:
Sorry, I think I expressed that wrong. What I meant was that someone might think that it is referring to the part of the framework ("unit") that does execution. Compare "Execution Filter" and "Execution Unit". I really don't think it's a good idea, and others have pointed out the same thing on IRC.- David On 19.03.2009, at 17:20, Noah Fontes wrote:-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 David Zülke wrote:That is bad, because it could also refer to the framework's internal "engine" to execute something.This is a moot point. We define the terminology. We need somethingsuitable that isn't ambiguous with existing terminology, not somethingthat could potentially be used maybe someday somewhere else. Noah -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAknCYrAACgkQhitK+HuUQJQ4vgCfRMwRFNfljYmQMmHUbh6hD/DE 1PYAoLeRJ0DfZuh9tuGfErmIAjh4vhKc =D6BD -----END PGP SIGNATURE----- _______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users_______________________________________________ users mailing list [email protected] http://lists.agavi.org/mailman/listinfo/users
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Agavi Dev Mailing List [email protected] http://lists.agavi.org/mailman/listinfo/dev
