Alex,
In developing the sites, what I would like to do, since I'm running on a dedicated server (as are a good portion of the people) and I have my own MySQL, I would like to pull the user registration/logon/etc information out of the "Links" database, into a USERS database.
I would like all my related sites to use/share the same user information, requesting the fields they need.
For a hard example, let's say I have 3 sites set up.
CreepyCards.com, Postcards.com and the PostcardsPortal.com.
I want _one_ user database between all the sites, and for my wwwthreads forum.
I want that same user base to be used for my catalog system, which while it might be separately installed on each site, for managing different product lines, it would still draw the user information from a central base.
That way, if I'm dealing with a user "troublemaker" I know it's the same ID across my entire network.
While it should be possible to do that, it would be _much_ nicer if the 'sensitive' information was able to be pulled into another database via an option during setup. Since you are working on the user system, I thought I'd throw this in.
Same would go for the advertising/banner system. If a separate database could be used as an option, then it would integrate with a network wide type of installation.
More importantly, it could divide the load across several servers, and separate the permissions and access to make it harder to breach the user database from the directory database.
Because of the way MySQL is set up, with each database as a file system, it would be in keeping with the "modular" and "object" way of thinking to have a "user" object that translated into it's own MySQL database object.
The point being, while keeping a user database inside a 'links' database is possible, and I'm actually doing some very funky legacy things, it would be much nicer (logically) to separate out the various "databases" _AS_ databases, rather than just tables.
make sense what I'm driving at??
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
In developing the sites, what I would like to do, since I'm running on a dedicated server (as are a good portion of the people) and I have my own MySQL, I would like to pull the user registration/logon/etc information out of the "Links" database, into a USERS database.
I would like all my related sites to use/share the same user information, requesting the fields they need.
For a hard example, let's say I have 3 sites set up.
CreepyCards.com, Postcards.com and the PostcardsPortal.com.
I want _one_ user database between all the sites, and for my wwwthreads forum.
I want that same user base to be used for my catalog system, which while it might be separately installed on each site, for managing different product lines, it would still draw the user information from a central base.
That way, if I'm dealing with a user "troublemaker" I know it's the same ID across my entire network.
While it should be possible to do that, it would be _much_ nicer if the 'sensitive' information was able to be pulled into another database via an option during setup. Since you are working on the user system, I thought I'd throw this in.
Same would go for the advertising/banner system. If a separate database could be used as an option, then it would integrate with a network wide type of installation.
More importantly, it could divide the load across several servers, and separate the permissions and access to make it harder to breach the user database from the directory database.
Because of the way MySQL is set up, with each database as a file system, it would be in keeping with the "modular" and "object" way of thinking to have a "user" object that translated into it's own MySQL database object.
The point being, while keeping a user database inside a 'links' database is possible, and I'm actually doing some very funky legacy things, it would be much nicer (logically) to separate out the various "databases" _AS_ databases, rather than just tables.
make sense what I'm driving at??
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
User Authentication and Logons