Ticket #72 (closed defect: fixed)
Execution modes are poorly named
| Reported by: | scorfield | Owned by: | scorfield |
|---|---|---|---|
| Type: | defect | Priority: | normal |
| Milestone: | Beta 2 | Component: | Miscellaneous |
| Version: | 5.0 | Severity: | normal |
| Keywords: | Cc: |
Description
Barney proposed changing them as follows:
development -> development-full-load
development-no-load -> development-circuit-load
development-parse-only -> development-no-load
The development mode would still be supported as a deprecated alias for development-full-load. In strictMode, Fusebox 5 would throw an exception if development mode was specified (and the exception would say it was deprecated in favor of development-full-load).
The documentation would then explain the modes as follows:
development-full-load is useful while you are modifying fusebox.xml a lot, early in the development cycle as it reloads the entire framework on every request - but it is not thread-safe;
development-circuit-load is likely the most common development mode: it is thread-safe but still reloads circuit.xml files whenever they change and always regenerates the parsed/ file - it does not reload the fusebox.xml file (use fusebox.load=true for that);
development-no-load is a useful mode when you are debugging a custom lexicon since it does not reload any of the XML files but still regenerates the parsed/ file.
To be honest, development-no-load is probably not very useful at all because development-circuit-load doesn't reload a circuit.xml file if it hasn't changed and therefore, if you aren't changing circuit files, development-circuit-load and development-no-load (-parse-only) would be exactly the same really...
