On Feb 9, 2007, at 9:12 AM, PRONZATO Cedric RD-BIZZ-GRE wrote:
A related problem is how to do "framework" components, I mean patterns. I think about my SMSC component, I base my code on the mail container and questions arised: - When do I have to make my own xml language (ie. MCA for the mail container)? - When do I have to make a Container? I guess the answer is if you have to manage the lifetime (create/release connections, ...).- When do I have to make an Engine? - ...So I guess we can finish with the following statement: "How to *use* is quite well documented but how to *make* is a bit less".
Have you ever found such a document for anything? My usual approach is generally something like:1. understand everything that exists, or research anything that is unclear 2. write something manually a number of times so you know what is always the same, and what varies
3. see if a paramerized tool would be helpful 4. apply a significant amount of "genius" 5. apply even more "sweat" to try stuff6. create an incredible tool or service or however it is best implemented
If there was a way to make creation deterministic, what would be the point of creativity?
-David
smime.p7s
Description: S/MIME cryptographic signature
