fix for some news problems we've been having. #95320 and #59449.

in the case where the socket gets closed we need to remove it from the
connection cache.  more work needs to be done to properly clean up
the protocol instance and to fix some related issues, but this helps
the end user.  r=bienvenu, sr=sspitzer.  thanks to Phil Anderton
for the patch.
This commit is contained in:
sspitzer%netscape.com 2001-09-19 00:19:43 +00:00
parent 90ed988ab8
commit ce42b3556e

View File

@ -5329,7 +5329,7 @@ NS_IMETHODIMP nsNNTPProtocol::CloseConnection()
if (m_nntpServer) {
m_nntpServer->RemoveConnection(this);
m_nntpServer = nsnull;
m_nntpServer = nsnull;
}
m_newsFolder = nsnull;
@ -5419,8 +5419,14 @@ nsresult nsNNTPProtocol::CleanupAfterRunningUrl()
nsresult nsNNTPProtocol::CloseSocket()
{
PR_LOG(NNTP,PR_LOG_ALWAYS,("(%p) ClosingSocket()",this));
if (m_nntpServer) {
m_nntpServer->RemoveConnection(this);
m_nntpServer = nsnull;
}
CleanupAfterRunningUrl(); // is this needed?
return nsMsgProtocol::CloseSocket();
return nsMsgProtocol::CloseSocket();
}
void nsNNTPProtocol::SetProgressBarPercent(PRUint32 aProgress, PRUint32 aProgressMax)