Click here to Skip to main content
15,880,405 members
Articles / Desktop Programming / MFC

Peer-to-Peer Communicator and File Transfer

Rate me:
Please Sign up or sign in to vote.
4.33/5 (57 votes)
14 Aug 20013 min read 390.1K   21.9K   167  
Get youself a peer-to-peer communicator and exchange files across a network.
// AcceptorThread.h: interface for the CAcceptorThread class.
//
// Written by Marat Bedretdinov (maratb@hotmail.com)
// Copyright (c) 2000.
//
// This code may be used in compiled form in any way you desire. This
// file may be redistributed unmodified by any means PROVIDING it is 
// not sold for profit without the authors written consent, and 
// providing that this notice and the authors name is included. 
//
// This file is provided "as is" with no expressed or implied warranty.
// The author accepts no liability if it causes any damage whatsoever.
// It's free - so you get what you pay for.//

#if !defined(AFX_ACCEPTORTHREAD_H__732CF9C5_669E_4ABC_A80C_80B423E83F5A__INCLUDED_)
#define AFX_ACCEPTORTHREAD_H__732CF9C5_669E_4ABC_A80C_80B423E83F5A__INCLUDED_

#if _MSC_VER > 1000
#pragma once
#endif // _MSC_VER > 1000

#include "NetThread.h"
#include "NetSockAcceptor.h"

class CNetConnection;

class CAcceptorThread : public CNetThread  
{
public:
							CAcceptorThread();
	virtual					~CAcceptorThread();

					bool	SetAddress(const string& strAddr);
             const char*    GetAddress() const;

			CNetConnection*	GetConnection() {return m_pConnection;}
    
protected:
	virtual			void	Process();
	virtual			void	Cleanup();
protected:
	CNetSockAcceptor*	m_pSockAcceptor;
	CNetConnection*		m_pConnection;
	string              m_AcceptAddr;
};

#endif // !defined(AFX_ACCEPTORTHREAD_H__732CF9C5_669E_4ABC_A80C_80B423E83F5A__INCLUDED_)

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here



Comments and Discussions