As part of the effort to speed up mozilla startup, we decided to merge cookie.dll and http.dll.

over to gagz

tell me more....

We want to reduce the number of dlls that get loaded at startup. Since cookie.dll always gets loaded with http.dll, dp and jud thought it would be good to merge the two. The actual discussion is on n.p.m.performance in a thread titled "Mozilla Startup Time". My post as part of the thread that describes the bugs I created is at news://news.mozilla.org/39176898.C79AE49E%40netscape.com.

the cookie dll handles an application perspective of the cookie service that HTTP allows. Unless this is really making a significant improvement I would prefer to keep them separate. warren brought out a related issue that suggests that we should keep all the misc. little dll's and group them together. I would still like to see some numbers that definitely indicate that clumping together makes things faster.

My perspective is that although http loads cookie, cookie.dll is an application thing. Other clients of necko won't want that stuff. I think cookie.dll should get packaged with all the other browser-specific dlls (e.g. history, bookmarks, etc.). Marking invalid.

verified invalid