Status update on Buxton. Please contribute! The project is already usable from the commandline, has unit testing and even some performance testing tools integrated, and runs extremely well in our tests.
Some details below - inline in my old status text. ==>> github.com/sofar/buxton On Thu, Oct 31, 2013 at 10:56 AM, Kok, Auke-jan H <[email protected]> wrote: > On Wed, Oct 30, 2013 at 8:58 PM, 김정훈 <[email protected]> wrote: >> Dear Auke, >> >> Here is the timeline of Tizen 3.0 Configuration System. >> >> Tizen 3.0 Configuration System: Agreed to move forward with new >> Configuration system that will provide client-server key-value support for >> Tizen 3.0. The timeline we agreed to is: >> • We start immediately with Auke-jan and Jung Hoon (David) Kim as the >> leads >> • Sept 30th: Initial draft of the specification / API definition on >> tizen3dev >> • Oct 15th: Prototype implementation for Tizen 3.0 to begin migration >> of VConf to new configuration system on tizen.org >> • Nov 15th: We would have migrated 6-12 services/apps. Prototype for >> notification will be implemented. Evaluate milestones beyond Dec 15th. >> • Dec 15th: The API will be frozen and all code available in Alpha >> quality. We're obviously a bit behind on the client side API, as we've not nailed down the ABI yet and there are still some methods missing. We'll have to adjust the schedule at one point. >> • Mar 15th: Beta quality code with VConf removed completely from Tzien >> 3.0 >> >> We need to check the current status of each items. >> If possible, could you send the draft version of API definition? > > Code is already well underway, but the client side API is not > finalized - it is being crystallized out at this point. > > Code is of course being developed here: github.com/sofar/buxton > > here is the status of the project: > > - the project contains about 10kLOC, contains testing framework tools, > is fully compiling, installable and running on any Smack enabled > system that meets the requirements > > - major components that are reaching feature complete: > 1) Service daemon core > 2) cli user client > 3) gdbm backend plugin > 4) memory backend plugin Most of these components are now maturing and unit tests are used to validate them. We have good confidence in most of these components being ready for more extensive client-side usage, and that's what we're also focussing on. > - current focus points are: > a) do layer resolution code and Smack enforcement This is about 75% done. The layer resolution code is finished, Smack enforcement is being done but we're still missing a few AC checks in the code, plus actually setting labels in the code is not yet complete. > b) initial client side API and library Still in progress. We're missing a client side API call, plus the actual client library API needs to still be finalized. > - "not yet" done - planned for later: > I) notifications This is 50% complete - notifications infrastructure code is present and we're getting to the final implementation of this code block. > The code can get/set values currently through the client socket API. I > ran a test and I can get and/or set about 70k keys per second through > a client socket connection (this was a quick test using a single key > to either store or read many times through the same connection). we now have a performance testing client to monitor performance: get_string: 100000 operations took 1.934s; Average time: 19.339us, sigma: 2.405us set_string: 100000 operations took 1.804s; Average time: 18.036us, sigma: 3.421us Cheers, Auke _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
