But this is the stuff applications [sic men] are made of ;-) If I follow you correctly the real beauty is that this type of technique could and should be used in any language. I think people who come to meetings like the CFUG are looking for those extra things that can make them better/more proficient and to "pick the brains of others". Unfortunately they do not come because we are all great guys (generically). Helping people understand how to apply this type of thinking also ultametly gives creditibility to the product as well. When we (as a community) can use the tools at our disposal more effectively to deliver higher quality products to our companies/clients, it increases the net worth of both the developer/development community and the tool set we use.
Your contribution to the group would be greatly appreciated. From: "Dan Blackman" <[EMAIL PROTECTED]> Date: 2003/03/04 Tue PM 10:36:23 CST To: <[EMAIL PROTECTED]> Subject: RE: persistence engine? MessageDon't go roping me in Dave! Joe, It's too detailed of a subject to address in an email, but I will tell you it is explained in detail in the book we wrote...Anthony McClure and Seth Hodgson wrote a few great chapters surrounding CFC's and persistence... The jist of it is that you have a each of your content objects inherit the methods of the base component and it, in itself creates a persistence layer that drives your application. It truly separates the Data Access layer from the Presentation Layer. I am creating an application now that has this functionality built in and you would be surprised how timely development becomes.... Dan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dave Cahall Sent: Tuesday, March 04, 2003 8:52 PM To: [EMAIL PROTECTED] Subject: RE: persistence engine? would be a GREAT topic for a CFUG presentation!!! -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joe Kelly Sent: Tuesday, March 04, 2003 7:49 PM To: DFWCFUG Subject: persistence engine? Dan, Could you go into more detail on this? Where could we get more information/examples of this concept. I think this is fascinating. From: CFC Bugs was Re: Problem with components as session The other thing I was going to add was that if you build a persistence engine for your apps then the need to write Add, Update, and Delete is removed... It becomes a simple invocation of the Add method of your engine...All of your objects can inherit these methods from a base component....Less dev time, increased time to market. We can now focus on the objects within our apps vs. being bogged down with building Add, Update, and Delete handlers...:-) Thanks, Joe KellyTitle: Message
|
Don't
go roping me in Dave!
Joe,
It's
too detailed of a subject to address in an email, but I will tell you it is
explained in detail in the book we wrote...Anthony McClure and Seth Hodgson
wrote a few great chapters surrounding CFC's and
persistence...
The
jist of it is that you have a each of your content objects inherit the methods
of the base component and it, in itself creates a persistence layer that drives
your application. It truly separates the Data Access layer from the
Presentation Layer. I am creating an application now that has this
functionality built in and you would be surprised how timely development
becomes....
Dan
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]On Behalf Of Dave Cahall Sent: Tuesday, March 04, 2003 8:52 PM To: [EMAIL PROTECTED] Subject: RE: persistence engine?
|
