> -----Original Message----- > From: Stephen Adams [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 12, 2006 5:33 AM > To: CF-Talk > Subject: Creating an API with coldfusion > > Hi, > > I'm thinking of developing an API for all the coldfusion work I'm doing at > work. I want to have a series of base components which I can reuse in > multiple projects. > For example I want to have a baseLogin.cfc, which handles some common > functionality for all logins. Then in a clients site I want to have a > clientLogin.cfc which extends baseLogin.cfc. > Has anyone done anything similar? What problems are there to look out for, > how did you structure your API?
Well - this is how I did mine: http://www.depressedpress.com/Content/Development/ColdFusion/DPLibraries/Ind ex.cfm This are collection of APIs (no interfaces, just the core "engines") for several common web application needs. For me one of the most important things was to create workable documentation. All of the CFC documentation on that page is generated from within the CFCs themselves (they're truly self-documenting). Of course this is pretty old (written originally for CF 5 and updated for CF 6) and I've little chance to work with CF any longer... but I'm still proud of much of this (especially the security system - very nice if I do say myself). Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:252834 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
