:) On 4/26/05, Barry Beattie <[EMAIL PROTECTED]> wrote: > >> . who's responsible to lock: the enabler or the enabler's client? I > can see both sides of the issue... > > aye, so can I and that's the problem...I even flirted with the idea of > the view doing the lock (but that's just wrong!) > > it all stems back to having a view-centric system where it's a request > for a file that sets the lock. and as I said, it's not as sophisicated > as having db connection pooling to cue access (where the whole problem > is shoved off to the db driver and db engine...) > > Jared, I like your enabler idea. I'm hoping to have the whole thing > abstracted enough that you don't know (or care) you're getting XML > data - the DAO just gets "data" and how is hidden elsewhere. > > thanx all for the input > > cheers > barry.b
-- --------------- ------------------------------------- Buy SQLSurveyor! http://www.web-relevant.com/sqlsurveyor Never make your developers open Enterprise Manager again. ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
