I used the nested set model for the v3.0 version of my CMS I wrote in the last three weeks. I am delighted with the ease of doing a lot of the CMS tasks - positioning parts of the site, moving chunks of site around, building sitemaps, all those kinds of things
Mind you, I'm not building it for hundreds of concurrent users, but at least for my purposes, i think its best if there must be a bottle neck, it ought to be in the CMS where the number of transactions a day will be but a fraction of the public side of the site. I'll happily trade a bit of overhead in the CMS for a speedier site generally any day. It sure beats the previous two versions of my CMS which were built around the adjacency model. Doing heaps of things are soo much easier with nested set for this application. Oh and by the say my new CMS is entirely run though CFCs using beans and DAO cfcs, with a central DAOFactory.cfc looking after all the instantiation of objects for the site. Frankly it was a dream to build it. It's the biggest and most complex app I've done using OOP cfc techniques so far, and I've seen that the more complex the app, the more treating cfcs as objects and passing them around makes sense. I was already a convert to OOP but now I'm even more a fan. Cheers Mike Kear Windsor, NSW, Australia Certified Advanced ColdFusion Developer AFP Webworks http://afpwebworks.com ColdFusion, PHP, ASP, ASP.NET hosting from AUD$15/month ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:230925 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
