That thing where the release notes
2013-08-13 21:51:07.825336+02 by Dan Lyke 1 comments
That thing where the release notes should have had a big "THE SOAP API IS GOING TO BREAK!", but didn't. And new documentation is silent.
2013-08-13 21:51:07.825336+02 by Dan Lyke 1 comments
That thing where the release notes should have had a big "THE SOAP API IS GOING TO BREAK!", but didn't. And new documentation is silent.
[ related topics: Invention and Design ]
comments in descending chronological order (reverse):
#Comment Re: made: 2013-08-14 01:22:06.043598+02 by: meuon
It's a SOAP API, It's going to break.
My current strategy is to accept whatever they send, write it out as a file, analyze what they sent and try to figure out how to respond. As the other end typically can't handle a real-time error anyway, (record #2345 is not valid.. ) this seems to work pretty well. Having a file or DB record of EXACTLY what they sent has been a life saver.
We will not edit your comments. However, we may delete your comments, or cause them to be hidden behind another link, if we feel they detract from the conversation. Commercial plugs are fine, if they are relevant to the conversation, and if you don't try to pretend to be a consumer. Annoying endorsements will be deleted if you're lucky, if you're not a whole bunch of people smarter and more articulate than you will ridicule you, and we will leave such ridicule in place.
Flutterby™ is a trademark claimed by
Dan Lyke for the web publications at www.flutterby.com and www.flutterby.net.