I've done this approach a number of times and quite like it. The parent site is just a consumer of your api. You become your own first beta tester and helps identify issues before you roll out to the public. Plus if you need changes made you make them directly to the api and not just your own site. That way you can always be sure what you are experiencing is the same as what a client is.
+1 for this approach. On Fri, Jan 28, 2011 at 9:19 AM, Eric Cobb <cft...@ecartech.com> wrote: > > 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:341680 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
