tag:blogger.com,1999:blog-3993498847203183398.post664558319563488605..comments2024-03-28T09:19:27.451+00:00Comments on RevK<sup>®</sup>'s ramblings: Clueless B2B XMLRevKhttp://www.blogger.com/profile/12369263214193333422noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3993498847203183398.post-14844245176040309742012-05-10T09:54:38.541+01:002012-05-10T09:54:38.541+01:00I'll get in touch with you by e-mail separatel...I'll get in touch with you by e-mail separately.<br /><br />As I think you already know, I have wanted this kind of access ever since we became wholesale A&A customers and have enough experience of E*tanet's wholesale interface to be able to tell you what it should have and what it should *not* have.Terry F.https://www.blogger.com/profile/13969846575454712191noreply@blogger.comtag:blogger.com,1999:blog-3993498847203183398.post-6691159844969933012012-05-10T08:59:40.758+01:002012-05-10T08:59:40.758+01:00Not sure of the merits of JSON as it is very easy ...Not sure of the merits of JSON as it is very easy to map XML to JSON in javascript (we do that a lot), but I guess it is something we could consider.<br /><br />I am trying to incorporate accounts details changes as well, e.g. address, email, password, etc. That will be challenging as accounts is a separate system with very tight access controls.RevKhttps://www.blogger.com/profile/12369263214193333422noreply@blogger.comtag:blogger.com,1999:blog-3993498847203183398.post-87843843101573280072012-05-10T08:46:36.452+01:002012-05-10T08:46:36.452+01:00Is it worth considering supporting JSON as well as...Is it worth considering supporting JSON as well as XML, as I've found this is proving more and more popular among developers as it removes a lot of the 'bloat' of XML and seems far easier to parse in most languages...Alexhttps://www.blogger.com/profile/08491808572691231544noreply@blogger.com