02:45:57 AM
3MF05XJ41
It might be a better choice to re-write the service in .NET and serve the data from a FoxPro COM object possibly.
you're talking of a .NET WCF service hosted by IIS, don't you? Let's assume I'll go this way. There are a few design questions to answer upfront.
1. The current Vfp clients need a new service wrapper instead of MSSOAP.SoapClient30. I can write it as a .NET DLL and register it for COM Interop. Any idea if this will affect performance when the response from the server is bigger than 10 MB?
2. Our SOAP client is configured for a 10 minute timeout and some of our users need this. How do I do this with a .NET service client?
3. With a SOAP 3.0 service IIS automatically loads as many instances of our Vfp MTDLL as there are parallel requests. After ach request the vfp MTDLL instance is dropped. Is this behavior different with a .NET WCF service? Or is there even a way to keep the Vfp DLL instance in memory and reuse it with the next request?
4. A WCF web service can be hosted by a Windows NT service. Does this change the answer to any of my previous questions?
TIA,
Markus
