Differences between revisions 2 and 3

Rename Application and Execution Context classes

The current pre-packaged execution context and application classes are not really named in a way that makes thie functionality clear.

The following is a proposed rename of the pre-packaged classes:

Current Class	New Class	Alternative Class
`SimpleContext`	`TemplateCtx`	`Context_stored_nowhere(?)` or `Context_no_store(?)'
`SimpleAppContext`	`ClientSessCtx`	`Context_stored_client`
`SessionAppContext`	`ServerSessCtx`	`Context_stored_server_process`
`SessionFileAppContext`	`FileSessCtx`	`Context_stored_server_file`
`SimpleApp`	`ClientSessPageObjApp`
`SimpleSessionApp`	`ServerSessPageObjApp`
`SimpleSessionFileApp`	`FileSessPageObjApp`
`ModularApp`	`ClientSessPageModApp`
`ModularSessionApp`	`ServerSessPageModApp`
`ModularSessionFileApp`	`FileSessPageModApp`
`RandomModularApp`	`ClientSessPageModByURLApp`
`RandomModularSessionApp`	`ServerSessPageModByURLApp`
`RandomModularSessionFileApp`	`FileSessPageModByURLApp`

The New Class identifies where the session is stored (ClientSess, ServerSess, or FileSess), specifies the page mechanism (PageObj, or PageMod), and optionally specifies that the page is selected ByURL. Execution context classes have a Ctx suffix and application classes have the App suffix.

In any event, if the KeywordArguments proposal went ahead we would not need any of these classes.

The problem with the Alternative Class is twofold; the scheme does not extend to the entire set of classes, and the naming convention does not follow the Python style.

-  ⇤ ← Revision 2 as of 2003-07-05 12:38:10 → 
  Size: 1232
  Editor: dsl093-191-107
  Comment:
+   ← Revision 3 as of 2003-07-05 13:44:40 → ⇥
  Size: 1777
  Editor: lon-cache2-1
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 9:
-|| `AppContext` || ||
-Line 13:
+Line 12:
-|| `Application` || || ||
-Line 20:
+Line 18:
-|| `RandomModularApp` || `ClientSessByURLPageModApp` || ||
|| `RandomModularSessionApp` || `ServerSessByURLPageModApp` || ||
|| `RandomModularSessionFileApp` || `FileSessByURLPageModApp` || ||
+|| `RandomModularApp` || `ClientSessPageModByURLApp` || ||
|| `RandomModularSessionApp` || `ServerSessPageModByURLApp` || ||
|| `RandomModularSessionFileApp` || `FileSessPageModByURLApp` || ||

The '''New Class''' identifies where the session is stored (`ClientSess`, `ServerSess`, or `FileSess`), specifies the page mechanism (`PageObj`, or `PageMod`), and optionally specifies that the page is selected `ByURL`.  Execution context classes have a `Ctx` suffix and application classes have the `App` suffix.

In any event, if the KeywordArguments proposal went ahead we would not need any of these classes.

The problem with the '''Alternative Class''' is twofold; the scheme does not extend to the entire set of classes, and the naming convention does not follow the Python style.