On Mon, 18 Mar 2002, Danny Epstein wrote: > I don't think opening a resource database consumes any more dynamic heap > than opening a record database. However, every time you access a > resource, the system searches through all the open databases to find it. > It can presumably skip over record databases pretty quickly. :) The > search stops as soon as the resource is found, so this won't affect your > app's resources much, but it could have more effect on system resources. > In practice, this shouldn't be a concern unless you keep a *lot* of > resource databases open.
Thanks for reminding me about that... yes, there could be quite a few open. I guess one thing I could do is to use a record DB and use record 0 as sort of an index (associating "resource" type/number with record index) to provide the benefit, without slowing things down elsewhere. Since nothing on the handheld should be modifying this database (it will be the result of a plug-in compilation elsewhere), then I shouldn't have any problem with maintaining the index. ----------------------------------------------------------------------- Brian Smith // avalon73 at arthurian dot nu // http://www.arthurian.nu/ Software Developer // Gamer // Webmaster // System Administrator "Genocide's the most exhausting activity one can engage in... next to soccer." -- Loki (Matt Damon), Dogma -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
