2 ms·
> Error replies should also include at least a short-text response (often along side a numeric one). I always try and design in a debug mode. Turn it on and th
by Gibbon1 8y ago
> Error replies should also include at least a short-text response (often along side a numeric one).
I always try and design in a debug mode. Turn it on and the destination will try to tell you exactly what you did wrong instead of stonewalling you.
Painful experience has taught me that you really want unique start and stop tokens, message type, message length, rev field and checksum/mac always. That at least allows you to mechanically validate and dispatch packets/messages.
- mjevans 8y agoCannot upvote enough building it //in//; and shipping it. Conformant implementations must include it and allow admins to enable it. You reminded me of the horror of talking to closed source things where there isn't even useful server-side debugging data. Stuff just fails or gets dropped without informing anyone why it went bad. This also applies to things like my credit card - I would love to have the last week or two of even /failed/ attempts at using my card in my online statement. That would really, really help with figuring out if someone was trying to use my card, or if a given service that rejected use of my card even tried to hit the CC company. (This happened with a major travel site which probably did it's own processing; having a firm direction to push and solid data might have helped.)