Hi, This is continuing on from a thread started by Janet McKay. If you're bored or irritated by terminology or patterns discussions, stop now! If you can write systems that work, I don't really care what you call them. Patterns hobbyists, read on.
The story so far... I said http://java.sun.com/blueprints/patterns/SessionFacade.html and Janet riposted with http://www.briankotek.com/index.cfm?fuseaction=content.viewcontentitem&conte ntid=47&returnto=coldfusion.main It's hard to critique demo apps because there's a lot of stuff in there just for example purposes. Anyway, Brian is a smarter guy than me, so hopefully he can tell me why I'm wrong. I can kind of see where Brian is coming from calling his CartManager a Session Facade in that CartManager seems to exist purely to provide locking to the session scoped Cart object, and this is analogous to the way in the Session Facade pattern you'll use a J2EE session bean to mediate access to non-reentrant entity beans. However, it kind of leaves out the fact that a primary motivator of the Session Facade pattern is to provide a course-grained interface for remote invocation. If you like, a Session Facade is a Remote Facade plus some concurrency management logicother problem I have with this approach is that as implemented it doesn't actually provide protection against race conditions. You are subscribed to cfcdev. To unsubscribe, please follow the instructions at http://www.cfczone.org/listserv.cfm CFCDev is supported by: Katapult Media, Inc. We are cool code geeks looking for fun projects to rock! www.katapultmedia.com An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
