Alex,
Again... PLEASE... abstract the User database so that it can be put into another databse in a simple fashion!!
It would be wonderful if this abstraction would apply to all tables, but specifically, the User/Sessions table there are multiple reasons to put it in a separate database, and really all the links program does is grab a record from it, or updated a record from it, once per iteration. Should be reasonably easy and straight forward for someone who knows the code.
Also, the "plug ins" such as the banners should be able to be abstracted out as well, if they run through links. But, this is not as much of a problem, since it's a "caller" program into a page, for the most part. But, being able to tie it to the User database/preferences/history would be a great thing as well.
Not asking you to write all this stuff (much of it is being done by others) but leaving it open for _easy_ integration into the program would be wonderful.
PUGDOGŪ
PUGDOGŪ Enterprises, Inc.
FAQ: http://postcards.com/FAQ
Again... PLEASE... abstract the User database so that it can be put into another databse in a simple fashion!!
It would be wonderful if this abstraction would apply to all tables, but specifically, the User/Sessions table there are multiple reasons to put it in a separate database, and really all the links program does is grab a record from it, or updated a record from it, once per iteration. Should be reasonably easy and straight forward for someone who knows the code.
Also, the "plug ins" such as the banners should be able to be abstracted out as well, if they run through links. But, this is not as much of a problem, since it's a "caller" program into a page, for the most part. But, being able to tie it to the User database/preferences/history would be a great thing as well.
Not asking you to write all this stuff (much of it is being done by others) but leaving it open for _easy_ integration into the program would be wonderful.
PUGDOGŪ
PUGDOGŪ Enterprises, Inc.
FAQ: http://postcards.com/FAQ
