Index: ossp-pkg/tabea/tabea-brainstorming
RCS File: /v/ossp/cvs/ossp-pkg/tabea/tabea-brainstorming,v
rcsdiff -q -kk '-r1.7' '-r1.8' -u '/v/ossp/cvs/ossp-pkg/tabea/tabea-brainstorming,v' 2>/dev/null
--- tabea-brainstorming	2002/07/04 06:54:48	1.7
+++ tabea-brainstorming	2002/07/04 14:46:32	1.8
@@ -379,6 +379,12 @@
     Issues:
     - [rse] $type should be not on constructor, but on render() IMHO
     - [rse] $prefix should be not on constructor, but on render() IMHO
+
+    [thl] agree on both. That came into my mind first but i thought a
+    switch between two types while the program is running will happen
+    almost never and having it fixed during the lifecycle of the
+    constructor might easy coding.
+
     - [rse] if thinking about programming a CGI, it is not clear to me
             how one has to process the POST data and inject it again
             into the $handle object for re-rendering. I would expect
@@ -389,6 +395,13 @@
                             - parse/render for input-device-specific I/O
                             - import/export for output-device-specific I/O
 
+    [thl] agree. I was thinking about render() being a hybrid function.
+    Note that the main program's "outer loop" will - must - preprocess
+    POST data because it might contain information unrelated to render()
+    or parse(). But i agree there are definitly two functionalities so
+    it shouldn't hurt putting them in two separate functions. In fact,
+    it might remove some magic.
+
     Example: Generic RAID configuration
     -----------------------------------