 NormanS Premium,MVM join:2001-02-14 San Jose, CA
·Pacific Bell - SBC
1 edit | reply to TheWiseGuy Re: [TWC] what could these "localhost" connections be?
said by TheWiseGuy :Now since in this case they are established versus listening, as was the case in the other example, you may be correct, all 4 sockets/ports may be simply for pollable events. I show four lines for the Firefox sockets. Each line treats one of the endpoints as local, the other as remote. Two loopback connections have four endpoints. I used 'netstat -ano' to get the ProcessID#. Windows Task Manager identified ProcessID# 5936 as Firefox.
-- Norman ~Oh Lord, why have you come ~To Konnyu, with the Lion and the Drum |
 TheWiseGuy Dog And Butterfly Premium,MVM join:2002-07-04 Yonkers, NY
| reply to jimkyle Yes I understand that you need a pair of ports/sockets for one connection. I should have made it clear that I was talking about ports/sockets not connections. From the post by EG that I cited
said by a firefox programmer :
I don't know how to implement NSPR pollable events on Windows without using a pair of TCP sockets, Now since in this case they are established versus listening, as was the case in the other example, you may be correct, all 4 sockets/ports may be simply for pollable events. Still in reading the complete reference I am not sure there should be more then 2 sockets/ports for the pollable events cited by that programmer, though it would make sense since the connection to check for a pollable event would be made to the listening socket and there normally are 2 listening ports/sockets. -- Warning, If you post nonsense and use misinformation and are here to argue based on those methods, you will be put on ignore. |