Some notes on the packaging: * I couldn’t find any documentation, or any doc-comments describing classes or methods. That’s going to make it very hard for anyone to learn how to use the library. * The implementation is also completely uncommented as far as I could tell. That makes it much harder for anyone else to diagnose problems, or to extend the library or fix bugs. * There’s no open source license given. You really should pick one and add it to the source code and as a separate LICENSE file. * Consider hosting this on Github or Bitbucket. It will improve visibility, make it easier to upload changes, provide an issue tracker, and make it possible for people to send you patches.
It looks like you’ve implemented a custom b-tree file manager. I know from experience that this is quite difficult (I’ve worked on Couchbase’s storage engine.) What led you to do this instead of using an existing engine like Kyoto Cabinet, LevelDB, LMDB, etc? I would worry about durability, especially. How does your engine recover from file corruption caused by a crash or power failure during a write? Since there are no docs I don’t know how the engine stores objects, or what its performance is like. When are objects loaded into memory or evicted from memory? When are in-memory changes persisted? Are there transactions? Can multiple processes use a database simultaneously? —Jens _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
