Webservice calls - SOAP

[Fairlight]

On Wed, Jan 21, 2015 at 01:21:01PM -0500, Walter Vaughan thus spoke:
> >The advice I would give is don't worry about the filePro portion until you
> have the requestor finished.
> >Be it .php, python, perl, or asp.net (I did one recently in vbscript for
> those who distain anything MS)
> >Have all the logic in the requestor and the last thing you do is drop a
> file to be imported by filePro.

I take an entirely different approach.  I use a perl transport layer
client for communications, and all business rules regarding assembly and
disassembly should be in filePro.  

You might use externals to convert the requests/responses (I have a full
suite which goes from CSV to XML (and optionally on to JSON), and a reverse
path for responses, for ease of export/import with filePro. filePro calls
those as necessary.  (Literally, one client could handle nothing but CSV
format, and can -still- do their REST API work due to this.)  

But bundling all the logic in a central place makes the most sense to me.

mark->
-- 
Audio panton, cogito singularis.