Click here to Skip to main content
15,895,142 members
Articles / Desktop Programming / ATL

An Asynchronous Pluggable Protocol Handler for data: URLs

Rate me:
Please Sign up or sign in to vote.
4.76/5 (21 votes)
28 Jan 2006CPOL5 min read 162.9K   2K   60  
This article describes an asynchronous pluggable protocol implementation to support the data: protocol, as described in RFC 2397, in Internet Explorer.
========================================================================
    ACTIVE TEMPLATE LIBRARY : DataProtocol Project Overview
========================================================================

AppWizard has created this DataProtocol project for you to use as the starting point for
writing your Dynamic Link Library (DLL).


This file contains a summary of what you will find in each of the files that
make up your project.

DataProtocol.vcproj
    This is the main project file for VC++ projects generated using an Application Wizard. 
    It contains information about the version of Visual C++ that generated the file, and 
    information about the platforms, configurations, and project features selected with the
    Application Wizard.

DataProtocol.idl
    This file contains the IDL definitions of the type library, the interfaces
    and co-classes defined in your project.
    This file will be processed by the MIDL compiler to generate:
        C++ interface definitions and GUID declarations (DataProtocol.h)
        GUID definitions                                (DataProtocol_i.c)
        A type library                                  (DataProtocol.tlb)
        Marshaling code                                 (DataProtocol_p.c and dlldata.c)

DataProtocol.h
    This file contains the C++ interface definitions and GUID declarations of the
    items defined in DataProtocol.idl. It will be regenerated by MIDL during compilation.

DataProtocol.cpp
    This file contains the object map and the implementation of your DLL's exports.

DataProtocol.rc
    This is a listing of all of the Microsoft Windows resources that the
    program uses.

DataProtocol.def
    This module-definition file provides the linker with information about the exports
    required by your DLL. It contains exports for:
        DllGetClassObject  
        DllCanUnloadNow    
        GetProxyDllInfo    
        DllRegisterServer	
        DllUnregisterServer

/////////////////////////////////////////////////////////////////////////////
Other standard files:

StdAfx.h, StdAfx.cpp
    These files are used to build a precompiled header (PCH) file
    named DataProtocol.pch and a precompiled types file named StdAfx.obj.

Resource.h
    This is the standard header file that defines resource IDs.

/////////////////////////////////////////////////////////////////////////////
Proxy/stub DLL project and module definition file:

DataProtocolps.vcproj
    This file is the project file for building a proxy/stub DLL if necessary.
	The IDL file in the main project must contain at least one interface and you must 
	first compile the IDL file before building the proxy/stub DLL.	This process generates
	dlldata.c, DataProtocol_i.c and DataProtocol_p.c which are required
	to build the proxy/stub DLL.

DataProtocolps.def
    This module definition file provides the linker with information about the exports
    required by the proxy/stub.

/////////////////////////////////////////////////////////////////////////////

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, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Architect
United States United States
This member has not yet provided a Biography. Assume it's interesting and varied, and probably something to do with programming.

Comments and Discussions