Re: [Blogcfc-develop] First big discussion

[Paul H. <pa...@su...>]

> N blogs per 1 DSN.
> N users per 1 DSN. (To allow for group blogs.)

move user management to db--handling it via text file sounds sadistic if you
go into dozens of users, blogs. you might retain the .ini file, its quite
convinient to boot up the app (only wish getProfileString did unicode, it
almost functions like simple java resourceBundle). the blog schema might be
changed to add column for "blog" to handle multiple blogs per table(s), just
need to specifiy which blog you want to return info from (this also makes
i18n the blog easier).  while you can try to normalize categories (for use
across multiple blogs), i can't see that as worth much effort.

if you're going to really make your blog i18n then a few things:
- better seperatation of text from presentation--this requires some thought
i think
- widen your sql "n" columns, maybe double them all (some maybe even more)
- lose the SQL_Latin1_General_CP1_CI_AS collation from the sql define script
- need locale discovery & logic (say you wanted to host a blog i18n buffet)
- i18n functionality beyond the LS function cf provides