Environment versions
Network:
Windows 2008 Server
Technically you are correct. But unless WWWC was already running on their server I would not argue for going that way - even if some vfp code needs to be called I'd argue for calling that from .Net Rest service via COM. Less "new" things to keep running smoothly on the server.
>If you would rather write the interface in FoxPro, I believe West Wind Web Connection supports SOAP and REST APIs. There would still be a learning curve and some setup, but maybe less if you don't know .NET.
>
>>Your point is valid. But I have so much work I am already spread too thin. And unfortunately I have not done anything with MVS; so this will be new to me too.
>>
>>>IMO, that's a bad idea. Making them write the receive piece gives them lots of access to your database and they may not implement it in a secure way. Remember.. this will be sitting on the Internet so you need to make sure the security is there. Also, if they implement it, you may not get the code. If the next customer comes along and needs something slightly different, you're back to square one.
>>>
>>>WebAPI is pretty straight forward, especially if you've done anything with MVC.
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