If and when CF gets to requests like you suggest below it will queue one and
process which ever one got there first. Think about it like a printer with
a print queue On a large network the persons print job that reaches the
queue first prints, but the other jobs are not lost. Same thing with CF, it
will hold one until the database if free, then do it's thing and move on.
Make sense?
> Ok....I read the post about the box to check to only allow 1 user
> to hit the
> DB at a time and let CF work out the rest. How does this
> work...what is CF
> doing and I am sure that it has an affect on performance. So someone
> hitting a page of dynamic content can be the only person hitting
> that page.
> Or if someone is updating the DB through a template they can be the only
> person hitting the DB. SO here is my question. If I have a
> editor running
> a template that is updating the DB at the same time as a client is hitting
> the main page with some dynamic DB content the client will get an error.
> Unless I have the box checked in CF. In that case what happens.
> I guess I
> just want a clarification of what the CF feature is that controls
> the 1 user
> in the DB at a time.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
