Sorry it’s been a bit quiet round here for a while. I’m settling into my new job now - it’s great to at last be coding for a full time job! It’s taking a while to get my head round the CMS we use and also the custom application development that has taken place which has ‘plugged’ into the CMS. Plugging applications so closely (ie. at a template level) into the underlying CMS seems an unwise architectural decision since there may come a time when these applications will need to be unplugged and plugged into another application.
Consequently, I’ve been writing a CFC based API calling the CMSs’ customtag API - my plan….to use my CFC API in my applications then further in the future I only have to modify my API to call the new products API and the applications should continue to operate. Well anyway - that’s the plan, whether it works or not is another matter…
January 22nd, 2005 at 7:55 am
interesting idea, but i’m not sure i follow your thinking about having an api which just calls their api.
Whats the benefit, wouldn’t it just add another layer of complexity? Cause everytime they have a product upgrade, you’d need to find out what they changed to the api and then alter your own api.
January 24th, 2005 at 4:08 pm
but every time they change the API there’s just as much risk that existing plugged in applications using the API will break…If all calls to the API are done by a CFC facade then the only place i’d have to update code is in the CFC and not have to go rooting through the application to find calls to the API. Plus you can write standalone test units to make sure that what you’re expecting out after you passed arguments in is what you’d expect…If the idea fails, i’ll be the first to post back here with further advice!
January 26th, 2005 at 7:02 am
Good point, best of luck with it