Re: Conf cache
"alex black" <[email protected]>
| Newsgroups | gmane.comp.lib.binarycloud.devel |
|---|---|
| Message-ID | <[email protected]> |
> I assume that the ConfCache can be written into this directory. > It is thus a cache per workspace. Right? Read more... no, we have a separate tmp/ directory in workspaces which would be used for this purpose. (so it would be BC_PATH_TMP . cache/conf/) if memory serves, I didn't check the exact path so it may be wrong :) > When Conf uses files, it be xml or php, a fileset can be defined for the > factory-level and a fileset can be defined for the workspace-level. I propose not to allow for any difference in XML. "factory" in xml should simply be example files included in the distro. (do people disagree?) > When Conf uses a database, a separate table can be defined for the > factory- > level and a separate table can be defined for the workspace-level. No - this should be a column in a single table. > I see no use for a level_flag since a workspace has a name and we must > distinguish between workspaces in the database. Correct ? No, since workspaces will nearly always share databases. Also if you have some strange custom setup where that is the case you can share one database between many workspaces and extend the schema to include the workspace name and write a "confServer" class to adapt to it. > Or is BC such that more than one workspace is not allowed? > Or should any workspace use a different database ? Yes, the latter - workspaces use different databases. > The alternative would be to prepend the path with workspace name. > Any voters yet? -1, don't like it. However I do not strongly dislike it, so if someone can show me why they think it is a good idea (with a real example), maybe I can be convinced :) > Now. the caching. Assume that caching is running ok. > This could be made intelligent, caching all on the fly. > Somebody changes some conf_values and wants to flush the cache. > So the caching starts freshly. Yeah you just delete the files in the conf cache path. > Possible solutions: > 1. flush them all. This one. _a _______________________________________________ dev mailing list dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected] http://lists.binarycloud.com/mailman/listinfo/dev