|
From: David S. F. <ds...@cr...> - 2005-03-14 14:51:18
|
Sorry its been awhile, I've been busy on other things. I think Infinity.adf is my homesite project file. I still use Homesite 4.5 for hand coding asp files. =20 Couple of comments. =20 As far as header.asp goes, this was just a proof of concept that you can have each state of a module be stored as pure html in a separate file and the main class can include what it wants depending on the state. If your objection is the fact that it is a header, I agree, we are better server rendering the base layout, template/header/footer in its own class. =20 You added support for returning rows to cDBConnection. I was abstracting the Recordset handling in cDBDataReader. The usage was demonstrated in the BuildPage method of cPage. I was trying to mimic ADO.net and abstract the ADO specific code. Another advantage of abstracting the methods, is that any major changes only need to be made in one file =20 I am kind of against API.asp. At the very least they should be contained within a class as that should be a goal of the design. I see no reason they need to be standalone. =20 cConfiguration is not live in memory and that's the beauty of it. It is a class and will only come into memory when initialized. Afterward it goes out of memory. If we do make it lookup values from a DB or properly structured XML file, it only need lookup and store values for that particular page. =20 I'm not sure what your point about the Connection String was. I do know we need to abstract the DB from each module, but that's a TBD item. =20 What in the engine are you looking to complete or design. When you say engine, do you mean the rendering engine, what loads and maintains each module instance.=20 =20 -David |