Eric... I like the idea of building out the API from the beginning. That would have the benefit of having your API almost fully tested before it's publicly released.
Simon Free has some great presentations on the Do's and Don't's of writing APIs. Check them out: http://www.simonfree.com/presentations/ andy -----Original Message----- From: Eric Cobb [mailto:cft...@ecartech.com] Sent: Friday, January 28, 2011 8:20 AM To: cf-talk Subject: Should I build my app as an API? I'm getting ready to start working on what I hope is to become a pretty large side project. Right now I'm in the planning phases, and one of the (eventual) plans is to have a full API that others can use to interact with the site. When thinking about this, I came up with an idea that I wanted to run by you guys to get some opinions. Instead of taking the usual approach of building the site like I want then adding an API to it, what if I were to just build out the API first, then build my site off of that API? Has anyone ever done this, or have any ideas on this? I'm really hoping to get a good discussion going on this, so please let me know what you think! -- Thanks, Eric Cobb ECAR Technologies, LLC http://www.ecartech.com http://www.cfgears.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:341681 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
