Hello, I'm doing a simple file download benchmark with firefox. By looking inside the log, it seems that
1) nsSocketTransportService::AddIdleList() and nsSocketTransportService::RemoveFromPollList() make the socket (connected to a web server and actively receving data segments) idle (i.e., removed from the next polling event). The consequence is that the next polling delays unnecessarily (in the sense that the socket is actually ready to be read from). 2) It seems that nsSocketTransportService::PostEvent() comes to the rescue to make the polling (i.e., select) return in not too long time. Why firefox has this design? Can I get some related documentations about this component? Or, could you please enlighten me by explaing about this mechanism? Thanks, Hwanjo _______________________________________________ dev-tech-network mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-network
