|
tartan version, reactor, coldspring
|
Angus Johnson
|
May 24, 2006 17:23 PDT
|
Hi Paul,
We're about to port a html (Mach II) application to Flex so I'm reviewing
the code base here and taking another look at the frameworks used. A couple
of questions regarding Tartan and future development...
The version in cvs seems stable but is it something that we could use in
production? Are there any immediate plans to modify the code further? I see
some comments in cvs referring to user defined factories and it looks like
the current code relaxes the requirement to extend tartan.DAO and tartan.VO.
Is that functionality complete or are there more mods to the framework to
come?
We have been playing with Reactor and would certainly look to use it for new
modules. I've been toying around with how this would integrate with Tartan.
Perhaps the best way would be to write a reactorWrapper that replaced the
standard DAOFactory. That would keep current method signatures. What are
your thoughts?
The new mystic updates to Coldfusion will change the way flash remoting
works with the automatic mapping of value objects. I need to delve into that
side a bit more but have you looked at how the current remoteservice may
change?
We have a significant investment in Tartan and I have resisted the urge to
look into yet another framework but getting a bit tempted by some of the
coldspring add ins like AOP. I see I could hook into Coldspring with the
wrapper to build beans and possibly build tartan services. Do you think
Tartan and Coldspring are two mutually exclusive beasts?
Lastly I'd just like to say that Tartan has worked out great and allowed us
to share a hell of a lot of common code. If I can cherry pick the
functionality out of the other frameworks that would be fantastic.
Cheers
Angus
|
|
 |
|
