Yup, the modparam part was so that u can have a diif db other than ser, so if u upgraded ser the scripts didnt make and mods for you.
Iqbal
On 4/27/2005, "Dave" ddx66@yahoo.com wrote:
Thanks. But are you refering to writing a module (modparam?)? I do not want to write a module. All I want is the my web application be able to configure ser and provision users. So in the case I would have two choices - user FIFO for ser management and direct database access for database manipulation. Right? --- Iqbal iqbal@gigo.co.uk wrote:
Hi
I think fifo writes to in memory DB which is read for things like aliases etc, hence if you are changing them then use fifo.
As for DB schema changing I think from the modparam lines you can change your table names etc for lookups on anything, (almost) which means that you can build you own DB structure, and then when a new version comes up, just compare the mysql.sh script used to see what new tables,columns were added.
Iqbal
On 4/27/2005, "Dave" ddx66@yahoo.com wrote:
I am thinking of implementing a web frontend to ser (similar to serweb) for internal use and would appreciate some feedback regarding:
- Is using the FIFO the best or the only way to
manage SER? 2) From what I see, I'd need to access the database directly for me to be able to add users, assign
groups
or even being able to insert AVP's. But this would imply modifying my code each time the database
schema
were to change in the future. Is there any better
way
to handle this?
Thanks in advance.
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam
protection around
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers