Transfer: Yes or no?

Posted At : July 16, 2008 8:58 AM | Posted By : Murloc Oracle
Related Categories: ColdFusion

A non-WoW related post? For realz?

I've been working on a Transfer/ColdSpring/ColdBox site. I've got one word for Transfer: voodoo magic. The powers-that-be for this project decided yesterday to abandon Transfer and go back to generating CFCs. I don't exactly know why it was abandoned, but it was cited that Transfer is causing more work arounds than its solving problems. Now I'm just a code monkey on this project. I pull down the files nightly, copy/paste what the other developer did, and change variable names until my portion of the work is done. So I don't have any problems with Transfer, I'm not involved in whatever hoops the other developer is jumping through to get stuff working. I can say I really liked Transfer for the short while I used it. It's shiny and new and from my perspective saves a lot of time.

Comments (2) | Print | Send | del.icio.us | Digg It! | Linking Blogs | 110 Views

Comments
[Add Comment]
I'd be curious to know why it was dropped.

Maybe it is something that can be fixed in a future release, or better documentation.

If you find out, please do let me know, as I've seen nothing on the transfer mailing list.
# Posted By Mark Mandel | 7/16/08 11:46 PM
I don't think it was dropped for any fault of Transfer. ColdBox and ColdSpring are new to the team as well, and getting three new things to talk with each other was straining the timeline for this project. From my view, Transfer was solving a lot of problems and is great for making everything consistent between the database and code. And it was a ton easier to learn than ColdBox. If I find out the exact problems they had with Transfer, I'll post it here.
# Posted By Murloc Oracle | 7/17/08 8:54 AM
[Add Comment]
BlogCFC was created by Raymond Camden. This blog is running version 5.9.002. Contact Blog Owner