You do realize that most of what you're asking isn't the function of a framework and the framework itself would really have no part in any of the items you listed. Also, as Dominic pointed out, Mach ii and ColdSpring address different areas of concerns. Mach-ii (and ColdBox and Fusebox and Model Glue and...) is a front controller framework that organizes your application files.
ColdSpring is a dependency injection framework that helps organize your CFCs (boy is that a high level overview). You use ColdSpring in conjunction with a front controller framework. How did you whittle down the choices to find yourself left choosing between those two particular frameworks? Why are you doing this at all, since you seem to be short on time and aren't familiar with frameworks in general? Just asking because, as a big fan of frameworks, I'd certainly urge you to move to one when and if the time permitted, or to factor it into your plans at some point. But if you're under the gun to get some development done in a short period of time... why add the learning curve for something new? That just doesn't seem to be the right point in time to undertake that particular effort. As far as your individual concerns... 1) I know that ColdBox has a caching mechanism, but I'm not sure that it's a database cache. You could use Transfer, which would probably be the more appropriate framework for caching database queries. Or CF 9 and its own caching mechanisms. 2) Really has nothing to do with your framework. 3) Really has nothing to do with your framework 4-6) Really has nothing to do with your framework. Again, an application framework like the ones listed above are largely to help organize how your application is structured, and create a clear and distinct layer between your model and your view, and implement a mechanism (the controller) that facilitates communication between the two. Frameworks aren't about certain features that can be built into your app. On Thu, Feb 18, 2010 at 8:48 AM, sandeep saini <sandeep00...@yahoo.com>wrote: > > Guys, > > We are creating a new website and i have to lay down the architecture for > that. Its basically a reporting tool which will fetch data from DB and > display. The data can be few records to Thousands of records depending on > search criteria. we have to create about 15 reports. The client wants a > strong archetecture. > > So which one of these would be a better choice. More basic requirements > are- > 1. Once the data is fetched, i would like to reuse that instead of going to > DB again and again. > 2. AJAX capability. > 3. Exporting data to PDF, EXCEL. > 4. Creating Mailing Lists/Labels and Sending emails thru the application > 5. Use stored procedures > 6. Easy to scale in case client wants new repots to be created. > > Experienced users, Your urgent reply is highly appreciated with a reason. I > need to make a decision very soon. also which one is simpler to implement of > these two as we also dont have much time just to create the architecture? > > Thanks > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Want to reach the ColdFusion community with something they want? Let them know on the House of Fusion mailing lists Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:330926 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
