Did some things automating IE, XmlHttp, COM based FTP and some WinInet stuff. Never had any real problems with timing, although only the IE stuff (screen scraping robot style) was used in hammering mode - back then line speed was limiting (ISDN and very early ADSL, last century stuff).

First tip: don't panic, do not worry too much in advance. Perhaps keep objects loaded and/or connection alive in certain situations. Measure/log where the bottleneck really is, act accordingly. For me XmlHttp was necessary for security reasons: Ricks WinInet stuff could not handle certificates back then and WinInet probably cannot access all protocols. Connection object should be replacable for such reasons and make you less vulnerable to performance lapses as a beneficial side effect ;-)

Rick uses WinInet in his vfp stuff and is probably best authority for speed issues if called from vfp on the planet, if you find a speed problem demonstrable in code with a real use case go directly to his board

>Hi there,
>
>as I am in the process of planning a new VFP-application I came across a problem I noticed when I compared two apps one written in vb.net and one in vfp using the wwipstuff-tools. In both apps I have implemented a http-based REST-Service which consists of a login, a request and a logout. So far, so good. But what I have noticed is that the VFP-App is slower than the vb.net-app.
>The first one needs 2-3 seconde, the second one 1 second. At first this sounds not to important but if it is used a hundred times or more it becomes important.
>What I would like to ask you is, if there ore other methods of implementing this via VFP, which are not wininet-based?
>I never used the MSXMLHHTP-stuff, does anyone know if it is faster? Or would it be better to use the .net-functionality in a com-server?
>
>Best regards and thanks in advance
>
>Thomas