|
From: Scott M. <sc...@cs...> - 2003-11-13 20:59:22
|
Eric, I am not sure what kind of performance hit this will produce.=20 Connections (opening and closing) are a resource heavy operation. A good=20= idea though. Give it a try! On Tuesday, November 11, 2003, at 11:09 AM, Eric Covert wrote: > Hey guys, > =A0 > I'm doing a few little sites right now for Tony Patrick, and I've=20 > convinced him to let me use the DNACMS. The one thing from Nuke that I=20= > would like to be able to give him is the ability to share the users=20 > table across sites so that people visiting these sites can use the = same=20 > username and password for each site. Now the way Nuke does this, is=20 > multiple sites will share the same database, and you give the tables = in=20 > the database a different prefix for each site. Then you tell nuke what=20= > the prefix is for the users table, and they all share it. > =A0 > If I was goind to implement this ability into the DNACMS, do you think=20= > I should go with a similar approach to that? I was thinking that a=20 > better option may be to let each site have their own database, then=20 > tell the CMS which of the databases to use for user info. I would = think=20 > that would be easier to manage instead of having multiple instances of=20= > each table in one database with different prefixes. However, that = means=20 > the engine will be connecting to two different databases (potentially=20= > on two different servers)... will that be a speed issue? > =A0 > Your thoughts? > =A0 > Eric > Best regards, Scott McCrindle Web Application Developer Certified Macromedia Flash MX Designer Compu-SOLVE Internet Services 520 Bryne Dr. Unit 6 Barrie, Ontario, CANADA L4N 9P6 Phone: (705) 725-1212 ext.107 Fax: (705) 725-1313 Toll-Free: (877) 567-6593 http://www.csolve.net |