Bárður Árantsson wrote:
> [snip]
> - or filesys
> - or ...
>
Of course. I had discarded filesys for the user:<user>/ hierarchy on
performance basis; It is nonetheless also applicable.
>
>> And the approach:
>> * filesys (direct) for init-like programs
>> * As soon as the daemon is running (libelektra checks if
>> /var/run/kdbd.sock is there), use the controller/slaves model which
>> Bárður has described before (a refinement of my original proposal). This
>> is the model used by many *high performance and secure* servers, such as
>> Apache and Postfix. Why not trust them for this? ;)
>>
>>
>
> The above is pretty much what I had in mind, though with the following
> implicit assumptions:
>
> - The mappings are static; that is, it is not possible to suddenly start
> mapping /blah/blahbhah to some different backend.
>
> - The actual backend used for the system/sw mapping is selectable by the
> system administrator.
>
> - The backend used for the user: mapping is selectable by the sysadmin
> and can optionally be overridden by the user. (This means "advanced"
> Elektra setups can be preconfigured by the sysadmin and that their users
> simply don't have to think about configuration at all and it will still
> work across multiple machines.)
>
Indeed. /etc/elektra/mappings is my suggestion for this, plus
.elektra/user.conf for the overrides.
Configuration could even be "overlaid" / "overridden" -- let's discuss
this when basic details are decided, shall we?
> > P.S.: I can write this a bit more detailed into a design document and
>
>> even put it into the Wiki (if given access, that is)
>>
>
> Doesn't everyone have access to write? I think you just have to login to
> be able to edit? (At least that was the case the last time I wrote
> anything on it... which is way too long ago.)
>
I couldn't login (I never had a valid login; my sourceforge.net login
didn't work either)
The "registration form" has been removed from the wiki, so I can't
signup myself nor request write access.
> Anyway, I think it is worth writing up into a design document, but it
> doesn't have to be super-detailed... I think just having everything
> collected up in one document would help a great deal when trying to
> understand the proposal.
>
I can only agree. Basically, condensing/collecting the thoughts exposed
here would suffice.
J.L.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Registry-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/registry-list
