Home

Hi there. If you're looking for some high level information on Taffy, you should check out the project homepage

To see exactly what's required to implement a REST API with Taffy, check out the Getting Started page.

There is also an Index of API Methods that documents what each does and how to work with it.

Why use Taffy instead of {another front-controller framework}?

Isn't Taffy just a front-controller framework? Why shouldn't I just use Fusebox / Mach-ii / Model-Glue / etc and some URL rewriting?

Yes, Taffy is just another front-controller framework for ColdFusion. And yes, it uses a similar url-formatting schema to most other frameworks — what most of them call "SES" or Search Engine Safe URLs. However, Taffy does have some key differences.

First of all, it's designed specifically for building REST web services. It doesn't try to solve any MVC problems, because there is no styling - just input and output. Secondly, this isn't your mom's SES URL formatting. We're not just encoding ?name=foo as /name/foo. Instead, you define that /artist/{artistId} represents a specific artist, and when the consumer requests /artist/17, your artist lookup method is passed an argument collection with: { artistId: 17 }. The "artistId" portion is not visible anywhere in the URL.

You could do something similar with URL rewriting, but defining and maintaining those rewriting rules would be annoying. I wouldn't recommend it, but you're free to try.

I think that if you give Taffy a try, you'll enjoy its simplicity.