So, if you don't have bagged samples of what they send, you can't validate for sure any hypothetical solution. They really can't send you a list of exactly what they send in each situation?
If you do have examples, you can make a table from them them.
Therefore, you can put the ones you've got samples of (which will be the common ones) in a table, and make guesses on the key words that will be kept from the middle of the response codes for the ones you don't have samples of. You can make sure that your guesses don't give false positives on any of the common responses. And make sure you have logging that will show you anything you get that isn't in your list of expected returns, so you can figure out what's going on and update your tables. This isn't excellent, but might be tolerable?
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
