Chris, for context, your reply to my post to n.p.m.performance is pasted below: > 7) bookmark.dll, search.dll, and directry.dll all get loaded when datasource > attributes with the corresponding "rdf:____" are encountered in navigator.xul > while building a content model. Can we load these datasources up after the > browser > window has come up? We'd talked about lazily populating the personal toolbar (which would allow us to defer loading bookmark.dll), but it didn't seem like a great idea. As for search.dll and directry.dll, we should be able to defer loading these by simply removing the "rdf:blah" from the menus that use them. (There are user interface issues with having dynamically loaded search results appear in a menu, anyway.)

Sorry for the spam. New QA Contact for Browser General. Thanks for your help Joseph (good luck with the new job) and welcome aboard Doron Rosenberg

rjc: i'm pretty sure that we've removed "rdf:files" (which is the directry.dll) from the menus. Could you confirm?

Removing "rdf:files" from the menus is bad... it would mean that "IE Favorites" wouldn't work on Windows. The search stuff should be in the menus as well, so that saved search queries work.

well, this DLL is gonna get loaded then, isn't it?

Loading these DLLs shouldn't be a problem, right? Aren't both directory.dll and search.dll really small? The biggest issue (I thought) with using these DLLs is that some of the menu code (I forget the bug #s) is aggressively over eager at creating content, and with these DLLs installed, they end up doing more work than they need to.

Right. Nisheeth just wanted us to look at removing unnecessary DLLs at startup, and well, these are necessary!