>Do you mean the web application passing XML to the VFP function as parameters, or the VFP function returning XML to be picked-up by (or posted to) the web application?

Either way.

>That sounds good. I've just taken a look at the article 'Building distributed applications with XML messaging' on your website and it has given me an insight into what's possible.
>
>A couple of questions...
>In one example you call the function XMLCursor using the command
>lcXML = owwXML.LoadUrl(;
> [https://www.west-wind.com/XMLCursor.wwd?Company=A])
>
>Q. Does the resulting string have to be stored to a variable? Could a 'results file' (eg. a uniquely-named csv file) be created on the server that can then be 'picked-up' by a later URL request or another application?

With that function yes. We have other tools (wwHTTP specifically part of West Wind Internet Protocols) that let you capture straight to file. But in the code above just use FILETOSTR().

>Q. Why the .wwd extension? Could it equally be .dll or .exe? Should I be building my function as an .exe, single-threaded .dll or multi-threaded.dll?

Never mind that. THat's the way my Web Server request handlers are setup. This is a script page (like .ASP or .ASPX). How you build your code depends on how you plug it in. If you're using in ASP.NET you will be building an MTDLL.

>What benefits are there (if any) to creating a web-service over the method you suggest above?

Web Services are more open and possibly easier to access for 'non-internal' clients.

However, if your own application is the client then not using a Web Service will be much more efficient.

+++ Rick ---