Hello Avi, Sriram and I have worked through a number of usage issues in the last day or so and are not blocked by any support issues at this time anymore.
For your info, we were missing some flags in the create entry code to indicate which nodes are to be treated as a directory type vs. a value type. We were also using the filesys backend, and were having problems due to this missing flag with the root directory not being created properly, and thus most operations following were not working. We also had some usage issues with writing the value data into the file. We are now in a happy place with the exception of one bug which is a by-product of the filesys backend. We cannot create a Key node with name "Foo" (handled as a directory folder on the file system) and a peer Value node (handled as a file on the file system) with the same name. To mitigate this, we are going to decorate all value node names with some extension so that there is no name collision. As we are writing an NT style Registry API equivalent wrapper over the Elektra APIs, our implementation will make the name decoration under the covers. We are also going to support all the NT style registry value types (REG_DWORD, REG_MULTI_SZ, REG_SZ, ...), since Elektra only support binary and string formats, we will store our data in a serialize format to add a type/length field in front of the raw data, and store it as binary. I joined the Elektra discussions group and as a result found the archives etc. which has helped to shed more light on the history and support that is in place so far. The impression I have about Elektra is that there is some momentum missing, and as a result there is a fair amount of holes in the completeness of it. This I determined from the comments on the web about the support of various bindings and backends. It is in need of some evangelizing to get adoption momentum in place. As Jerry pointed out, we are keen to leverage this within our product for storing system settings and Group Policy settings that should be applied to system components. Maybe we will be able to help configure the systems we are installed on with Elektra, and start to seed the system registry with settings to be followed. I did have a few questions though that I'm curious about: I was curious why your APIs were not modeled in a way similar to NT, is there a possible IP concern? Or is the flexibility of back-ends and bindings what led to the design? If there is a goal to centralize all data into a common system store, it would seem confusing to allow application writers the choices of backends and where each may store their data. Have there been any thoughts on a backend that models the windows registry hive, which is perhaps loaded in like a memory mapped file? Would you be interested in having the NT style wrapper interfaces we are writing to include with Elektra SDK? Thanks, Glenn Curtis Software Development Centeris Corporation -----Original Message----- From: Gerald (Jerry) Carter [mailto:[EMAIL PROTECTED] Sent: Thursday, February 01, 2007 8:36 PM To: Avi Alkalay Cc: [email protected]; Glenn Curtis; Sriram Nambakam Subject: Introductions and hitting some issues -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Avi, Long time since the Summer of Code project. I'm still trying. btw....we have picked up some more registry support in Samba just not the libelektra integration yet. Still probing at it. I wanted to introduce Glenn Curtis and Sriram Nambakam, Both are devs at Centeris (where I work). We have an Active Directory group policy agent for Unix/Linux and are trying to use libelektra for the storing policy settings. Apparently we have some problems in the key/value storage. Glenn will expand on this in another mail (which is the reasons why I'm making the introduction for him). We're on 0.6.6 IIRC dealing with Linux, Solaris, AIX, and HP-UX. Our goal is to push patches upstream to you folks as necessary and appropriate. And to provide environment integration with open source applications. The Likewise Identity product just released last month and is at http://www.centeris.com/products/. We do a lot of Samba work of course. Right now the group policy agent is proprietary in order to pay the bills. You know how that goes. I just wanted to let you know what was going on and get Glenn and Sriram talking to everyone else. cheers, jerry ===================================================================== Samba ------- http://www.samba.org Centeris ----------- http://www.centeris.com "What man is a man who does not make the world better?" --Balian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFwr+XIR7qMdg1EfYRAgfxAKCUDkyWUAK3GzfeHGdhXYnYd0mPegCg0w5u JOQHGvN/87oGqaXEn2CpRuQ= =UN0z -----END PGP SIGNATURE----- ------------------------------------------------------------------------- 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
