The most suitable representation for data-types is determined when they are allocated. The code that does the determination is set up by this file. To override the defaults, simply re-implement the 'new' method for the classes of your choice before y...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCJPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTC
Support for extremely efficient records. Even without optimization or benchmarks, the memory savings achieved by factoring the hash keys is quite significant and a large performance win. Perl implements a similar strategy by globally sharing hash key...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCEXPERIMENTAL package to integrate ObjStore transactions with Event. Implements dynamic transactions. Great service is key....
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCWe go through hoops to make it easy for newbies. Use this module if you need to do something fancy. Here is a list of fancies: * $ObjStore::CACHE_SIZE * $ObjStore::CLIENT_NAME * $ObjStore::SCHEMA_DB Some of these variables can also be set via environ...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCDeclares a simple stub method that invokes the "notify" method. Works in concert with "ObjStore::Process::autonotify". There will probably be a way to alias this package to 'notify', so you can type 'use notify' instead of 'use ObjStore::notify'....
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCUnstructured perl databases are probably under-constrained for most applications. Tables standardize the interface for storing a bunch of records and their associated indices. A table is no more than a collection of indices (as opposed to a some sort...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCJPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTC
An active database is an framework for tightly integrated collaboration. While implementation abstraction is preserved without hinderance, objects can easy interact in a variety of ways: * ABSTRACTION / COLLABORATION The hash at the top of the databa...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCThis hook should not be used unless it cannot be avoided. There is a significant performance penalty compared to immediate destruction. However, one good reason to use this mechanism is to ease the syncronization constraints when multiple processes a...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCThe minimum amount of database code to reasonably represent a Unix process. Patches for non-Unixen welcome....
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCI'm not sure if this will be depreciated......
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTC$at = TABLE ObjStore::Table2 { [10] of ObjStore::HV { row => 1, }, indices: ROW; }, Unstructured perl databases are probably under-constrained for most applications. Tables standardize the interface for storing a bunch of records and their associated...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTCImplements an API very similar to "ObjStore::Index", except with an array implementation. Elements are unsorted. Both "add" and "remove" always scans the entire set. This might seems like a joke, but keep in mind that O(N) complexity algorithms takes...
JPRIT/ObjStore-1.59 - 27 Apr 2000 14:22:09 UTC