portal entry

select a category, or use search below
(searches all categories and all time range)
Title:

Taffy for REST – Part 1: Setup

| View in Portal
October 25, 2018 04:49:26 AM GMT
1 Comment
<p>TaffY: The REST Web Service Framework for ColdFusion </p>
<p>The post <a rel="nofollow" href="https://coldfusion.adobe.com/2018/10/taffy-rest-part-1-setup/">Taffy for REST – Part 1: Setup</a> appeared first on <a rel="nofollow" href="https://coldfusion.adobe.com">ColdFusion</a>.</p>
Labels: Blog, Third Party Solutions, blog, framework, rest, third party solutions

Comments:

Hey, James. Thanks for this series. I have only gotten to watch the first, but I do have a question that I don't see it addressed here nor was it in the video. Others may have it, right out of the box in considering all that you offer here. <em>Can you talk about why you chose and would still recommend Taffy over CF's built-in REST features (added in CF10)?</em> I don't say that at all to knock Taffy, but just because it would be a sincere question many would have, in contemplating the two options. While initial discussions comparing them were focused on CF10 and from 2012, the CF REST feature did evolve, first in CF10 updates and then also in CF11, fixing many things that initially troubled first explorers. Of course, Taffy had existed before, and served folks on CF9 and earlier. But I know Adam had different ideas than how the CF team did things. And clearly Taffy still serves people today, as your 2018 video shows. It would just be helpful to hear from a modern-day Taffy fan (and blogger like yourself) who could compare the two, and help people assess each for their needs. Some will notice Taffy was last updated in Mar 2016 (before CF2016 came out). I will add that I don't know of any language changes in CF 2016 or 2018 regarding REST, so even comparing it just to CF's REST as of CF11 would help those still on that (though since CF11 is no longer updated by Adobe, it would be unwise to still be running on that or older versions.) Finally, though the CFML language doesn't seem to have changed regarding REST support in CF2016 or above, readers should note that CF2018 did add a REST Playground feature that may interest them, and of course CF2016 Enterprise had added the API Manager for managing APIs of all sorts (it's technically separate from CF, and useful for APIs created or called in any platform). Hope that's helpful to some readers. And James, maybe that comparison would make for a useful new blog post for you, if it interests you. Either way, again, thanks for the substantial series as-is.
Comment by Charlie Arehart
2169 | July 18, 2019 03:12:41 PM GMT