Hi David,

Yep, you set the URL in web monitor (doesn't have to be a WC site) and it looks at what comes back (searches the HTML returned for a specified string). I'm not sure of the internal workings of the Web monitor, but I guess you're probably right about HttpGetEx.

I've certainly not seen IIS "screwed in a special way" as you describe <g>, but it's worth looking at the web monitor. My understanding is that you're licensed to use it if you've bought WWWC.

If your URL is on the outside (not an intranet) and you'd like me to test Web Monitor against it for you, drop me an e-mail.

Have fun with FoxISAPI.

Cheers,

Andrew

>G'Day mate,
>It's a piece of cake to right the app actually and send emails. But I'll look at it of course. But the Wininet DLL call is hanging every attached app if IIS is hung or screwed in a special way, which I don't think you see every day. (I believe it's being caused by a related email problem on the network with huge numbers of emails being thrown around - some 30,000/hour)
>So the WW Web Moniter would probably suffer the same fate since Rick would still be using the httpgetex I bet.
>Also we're not using WWC on the site, we have our own scripters running over x-works, soon to be Foxisapi (we hope) XWorks works great and is fast but the author has taken a dive! So the move to FoxISAPI actually looks fairly simple now that MS have built a decent one (or maybe it's the Rick Strahl version :-)
>So do you know if WW Web Monitor will monitor any page request?
>David
>