Jon,
For starters, you are going to want to read up on the section of the
MSDN documentation titled "Exposing .NET Framework Components to COM",
located at:
http://msdn2.microsoft.com/en-us/library/zsfww439(VS.80).aspx
As for your particular interfaces (IInternetProtocolRoot,
IInternetProtocolSink, and IInternetProtocol), you are going to have to
define those in your code (with the appropriate marshaling attributes, which
are specified in the link above) and then access them appropriately.
You might also want to look in the header/idl files that these are
defined in, as you will need the IID (interface ids) in order to define them
in .NET.
Looking at http://www.pinvoke.net, there are definitions for the
interfaces you need:
IInternetProtocol -
http://www.pinvoke.net/default.aspx/Interfaces/IInternetProtocol.html
IInternetProtocolRoot -
http://www.pinvoke.net/default.aspx/Interfaces/IInternetProtocolRoot.html
IInternetProtocolSink -
http://www.pinvoke.net/default.aspx/Interfaces/IInternetProtocolSink.html
You can use these definitions, and then just focus on the
implementation.

Signature
- Nicholas Paldino [.NET/C# MVP]
- mvp@spam.guard.caspershouse.com
From what I gather, I need:
IInternetProtocolRoot::Start
IInternetProtocolSink::ReportProgress
IInternetProtocolSink::ReportData
IInternetProtocol::Read
...the problem is, I've never worked with COM interfaces before, and I
have no idea how I would write this. Even more general code that
showed how to implement COM interfaces would be helpful.
--Jon
On Dec 24, 12:11 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:
> Jon,
>
[quoted text clipped - 24 lines]
>
> - Show quoted text -
jcorbett@fourtentech.com - 24 Dec 2007 17:51 GMT
Cool, thanks! :)
--Jon
On Dec 24, 12:40 pm, "Nicholas Paldino [.NET/C# MVP]"
<m...@spam.guard.caspershouse.com> wrote:
> Jon,
>
[quoted text clipped - 76 lines]
>
> - Show quoted text -
christery@gmail.com - 25 Dec 2007 22:16 GMT
Googling on ISAPI might help
Just a thought
//CY
Arne Vajhøj - 26 Dec 2007 01:10 GMT
> Googling on ISAPI might help
AFAIK then ISAPI is a server side technology.
Arne
christery@gmail.com - 26 Dec 2007 12:57 GMT
> christ...@gmail.com wrote:
> > Googling on ISAPI might help
>
> AFAIK then ISAPI is a server side technology.
>
> Arne
Yepp, api:s for controlling the IIS before it makes something...
I was thinking about talong the example of setting up a chatt and then
filter
out bad words (profanity filter) on a server that I can control (and
can be sued if missused) with isapi...
Not filtering the client, there should be a lot of parental control
tools for that without programming...
//CY
christery@gmail.com - 26 Dec 2007 13:04 GMT
For a MIME parser (Mail not HTML) in cs there is
http://www.codeproject.com/KB/cs/mime_project.aspx
//CY
Lew - 26 Dec 2007 15:24 GMT
> I was thinking about talong the example of setting up a chatt and then
> filter
> out bad words (profanity filter) on a server that I can control (and
> can be sued if missused) with isapi...
I don't know about lawsuits, but profanity filters can cause trouble. For one
thing, the definition varies with culture - in parts of the English-speaking
world the adjective "bloody" is more profane than in others. Also a
discussion like this one, where a word might be cited in an analytical
context, probably shouldn't be filtered as strenuously as a flame rant.
AOL got in trouble with a profanity filter a few years back when all the
members of a breast cancer survivor support community got blocked for having a
discussion about "breasts".

Signature
Lew
christery@gmail.com - 26 Dec 2007 18:49 GMT
> AOL got in trouble with a profanity filter a few years back when all the
> members of a breast cancer survivor support community got blocked for having a
> discussion about "breasts".
>
> --
> Lew
Yeah, heard about one that filteerd pics of pigs out, parent control
thinking it was bare skin...
or that might have bean "a rat in the pizza"... never tried it (parent
control at home...), we use surfcontrol at work and it banns all
search eng. like yahoo, alltheweb, but not google
bcause its a lot of not nice words there... but it can be adjusted...
think google was fixed first... or found first then we take them one
by one... (allowing search eng. - not results)
Ohh, really off point... *sorry*
//CY