Bender Expansion
I have just concluded a magnificent conversation with the brilliant Mark Mandel of Transfer fame - we spent about 25 minutes each trying to convince each other of pretty much exactly the same thing :)
The upshot is that while I've been focused just on getting direct communication between flex and transfer, Mark has been asking questions about looser coupling to CF models - for example Bender being able to pass transfer objects to other gateway cfcs (or retrieve data FROM other cfcs) instead of talking directly to transfer. What I think I'll do once I have the basics working, is set it up so that Bender can act either as a direct translation layer to Transfer, or as a proxy to other model cfcs in a coldfusion applications, via the mapping of transfer objects to cfcs and methods in an xml file.
This way Bender will allow you to setup a mapping that says, "When I try to save a Page object, send it to the PageManager's save() method" instead of Transfer.save() directly. this will allow for further business logic without breaking existing models. The simplicity of simply throwing actionscript model data directly at transfer will still be there, and would be the default operation if no mappings are setup, but this will allow for much more flexible usage. Again - comments very welcome, I see lots of readers but no suggestions! :p
Thanks again Mark for the advice.
http://www.tobytremayne.com/trackback.cfm?D54741D1-A3BD-5FFD-EE6A8C0AC06D6FD4
Do you want to show off some sample code of how it will work?
That usually gets some comments.
A few of us in CFFlex were talking about Bender and the potential architecture. Perhaps it was late where you are, but people are definitely interested. I put up a quick post here:
http://www.nodans.com/index.cfm/2007/4/9/Is-Bender...
please correct any inaccuracies as you see fit.
There is some good interest in the bender concept.