Dan Mosedale wrote:
> [adding a cross-post to .netlib] > > [EMAIL PROTECTED] writes: > >>When mozilla 20011015 does name resolution. Is it using the libraries >>from the system, or is it doing it itself, by generating the >>UDP packets, or what? >> > > It uses gethostbyname() from the system resolver. this is true for XP_UNIX, XP_BEOS, and others, but not true of XP_MAC or XP_WIN, which use other native resolver methods. for example, the XP_WIN code uses the winsock asynchronous resolver api. > > >>I'm trying to find out why it's so damn slow... >>DNS lookups on my system are snappy & fast (nslookup, host and good old >>ping). yet mozilla sits there for 30 seconds or so pissing around doing >>nothing except saying it's resolving the name... >> > > One possibility is if you've got two resolutions going on > simultaneously in Mozilla, one could be stalling the other (see > http://bugzilla.mozilla.org/show_bug.cgi?id=70213). Probably more > likely is that resolution has actually finished, but gecko itself has > not updated the status bar; I believe there are known issues with > that... perhaps someone in the know (Gagan?) could reference the > relevant bugs. i can't recall the bug number(s), but this is definitely the problem. a packet trace will confirm that DNS resolution happens very quickly. somehow, it seems that the next status message (ie. connecting to...) is lost/delayed. darin
