|
From: Eric C. <e_c...@ro...> - 2003-11-11 16:09:40
|
Hey guys, I'm doing a few little sites right now for Tony Patrick, and I've = convinced him to let me use the DNACMS. The one thing from Nuke that I = would like to be able to give him is the ability to share the users = table across sites so that people visiting these sites can use the same = username and password for each site. Now the way Nuke does this, is = multiple sites will share the same database, and you give the tables in = the database a different prefix for each site. Then you tell nuke what = the prefix is for the users table, and they all share it. If I was goind to implement this ability into the DNACMS, do you think I = should go with a similar approach to that? I was thinking that a better = option may be to let each site have their own database, then tell the = CMS which of the databases to use for user info. I would think that = would be easier to manage instead of having multiple instances of each = table in one database with different prefixes. However, that means the = engine will be connecting to two different databases (potentially on two = different servers)... will that be a speed issue? Your thoughts? Eric |