I would advocate using JSON over XML. JSON is less wordy (important over the wire) and is essentially serialised JavaScript. If you are working with web services on other platforms in the future I would say that JavaScript will be the lingua franca.
In terms of VFP and JSON, I have used Craig's library in a production environment. That project involved a Visual FoxPro EXE running as a Windows service, which serialised DBF data and sent it to a web service. It worked 95% of the time but (IIRC) I kept hitting edge cases that would cause it to fail. As a result I ended up just rolling my own JSON and calling the 'sanitisation' routines in Craig's library to encode it properly for the wire. Ultimately I redid the whole thing using C# and JSON.Net. If I had to use VFP again for a similar thing I would probably look at the JSON functionality in West Wind Software's West Wind Web Connection. As great as Craig's stuff is he seems to be otherwise engaged these last few years, and I imagine you would get better help and support from a paid solution. _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
