I discovered that, if you create a com object for use in conjunction with FOXISAPI, the existing object is released everytime it is requested to activate a non-existing method.

If you do the same under vfp .. you just get a controllable exception. The object is not destroyed.

Curious and annoying as it possibly means that you can hammer out a FOXISAPI-based site by repeating calling such a non existing object...

The server com objects just die repeatingly on each call and have to be resinstantiated regularly! In view of the size of vfp objects (blurbs) such an attack would be very cpu-intensive.

Is it a bug? does it also affect west-wind connection? is it "per MS design"? or am i missing something?