On Thu, Dec 12, 2013 at 6:28 PM, Emmanuel Lécharny <[email protected]>wrote:
> Le 11/15/13 1:41 PM, Emmanuel Lécharny a écrit : > > Le 11/15/13 12:08 PM, Kiran Ayyagari a écrit : > >> The name "BTree" is used for both in-memory as well as managed types > >> this might be slightly confusing unless one looks at the package names. > >> > >> I suggest we name them as > >> > >> 1. BTree - the type of tree that maintains data in-memory only > >> (Note that this type of tree also supports an option > to > >> flush data to disk with the help of a journal, but > may not > >> guarantee data persistence unless explicitly flushed > by > >> the user) > >> > >> 2. PersistentBTree - the type that persists data to disk > >> > > I agree there is a confusion between those two names. This is also true > > for many classes : > > Page, Leaf, Node, *Result, TupleCursorImpl, Transaction, ParentPos, > > BulkDataSorter, BTreeFactory, BTreConfiguration, BTreeBuilder. > > > > There is probably some renaming needed here. > > > So what about : > - InMemoryBTree for in-memory BTree > - PersistedBTreefor managed BTree > > +1 > and let the BTree becomig a shared interface ? > > +1 I suggest we name it AbstractBTree > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > > -- Kiran Ayyagari http://keydap.com
