Hi!
The user database is abstracted. You can integrate both sessions and authentication with Links SQL not only from another SQL table, but from any method be it server based authentication, flat file sessiosns, username/password lookup in text files like ubb, etc.
Links SQL still needs to maintain its own information about users that it needs to store somewhere. It doesn't make sense, and may not even be possible to store that information in somewhere outside of Links SQL's control.
To integrate with another database you simply plug the calls to add and del users, authenticate sesions and change passwords into the Authenticate module. I will make this editable from the admin though.
I see this as the most extensible way. We can provide several pre-built Authenticate modules to connect to a variety of sources like vbulletin, wwwthreads, or whatever.
Or am I not understanding what you are asking?
Cheers,
Alex
--
Gossamer Threads Inc.
The user database is abstracted. You can integrate both sessions and authentication with Links SQL not only from another SQL table, but from any method be it server based authentication, flat file sessiosns, username/password lookup in text files like ubb, etc.
Links SQL still needs to maintain its own information about users that it needs to store somewhere. It doesn't make sense, and may not even be possible to store that information in somewhere outside of Links SQL's control.
To integrate with another database you simply plug the calls to add and del users, authenticate sesions and change passwords into the Authenticate module. I will make this editable from the admin though.
I see this as the most extensible way. We can provide several pre-built Authenticate modules to connect to a variety of sources like vbulletin, wwwthreads, or whatever.
Or am I not understanding what you are asking?
Cheers,
Alex
--
Gossamer Threads Inc.