From: Wolfgang M. <wol...@ex...> - 2011-02-18 08:49:05
|
Good idea. It would help to hear more. Dmitriy, would you be available for a chat today? If yes, I'll announce a teleconf. Wolfgang Am 18.02.2011 09:25 schrieb "Dannes Wessels" <di...@ex...>: > In all, a nice subject for a dev telecon? > > Sent from my iPhone > > On 17 feb. 2011, at 12:54, Dmitriy Shabanov <sha...@gm...> wrote: > >> >> >> On Thu, Feb 17, 2011 at 3:04 PM, Stefan Majewski < ste...@un...> wrote: >> On 17/02/11 09:26, Adam Retter wrote: >> I really feel that this *must* go in /db/system. As a user I dont >> really want my databases becoming polluted with configuration files >> that are not part of my application. >> >> I really do second this. I use the collection name "etc" in several/most applications, as I usually need a place to put my App's configuration. Then, in case I deploy the application to my top-level database directory (what I rarely do, but nonetheless) I would probably face a conflict. From a user perspective this seems to be just another name to avoid. >> >> That is what it for .... mean pluggable applications ... what permissions do you set to this collection? and it should not generate any conflicts, because on restore permissions can be changed any way. >> >> All I need is collection that exist by default and pluggings don't need to worry about. >> >> -- >> Dmitriy Shabanov >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Exist-development mailing list >> Exi...@li... >> https://lists.sourceforge.net/lists/listinfo/exist-development |