No, I mean you can make the VFP component a web service using the Web Service wizard that comes with VFP.
The advantage of Web Service over COM is great if you are on the internet, in an intranet some of the advantages go away. The main issue being rights to the COM object.
BOb
>You can create WebService that calls VFP COM component (but then why not just use COM component directly.). I never tried it myself though.
>
>>Can you make the VFP object a web service. I know this uses COM interop, but it happens internally so it may be faster.
>>
>>>Run some tests using both methods and let us all know which one is better:)
>>>
>>>>Looking for a "good blanket statement" (oxymoron?) about some COM-.NET architecture. I am trying to determine if it's faster to pass a string of XML from a .NET assembly to a VFP MTDLL (the MTDLL is inside a COM+ app so it's always "on"), or if it's faster for the .NET object to write the XML to disk, pass the filepath to the MTDLL, and let the MTDLL to FileToString().
>>>>
>>>>
>>>>
>>>>Any thoughts?
>>>>
>>>>Thanks.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only