- This topic has 12 replies, 5 voices, and was last updated 14 years, 8 months ago by .
Can I get a sanity check here before bring this up with the vendor? I’ve been testing a new TCP/IP interface and it’s been very spotty. I’d send it an HL7 message and wait, and send it again and wait, and again and again. And then, all of a bunch of acknowledgements all at once.
It turned up the noise on the engine output, and I see all of the acknowledgment messages strung together in the hex dump and then it seems that Cloverleaf is gracefully breaking up each ACK and processing them seperately.
I’m thinking that they’re acks are building up in their outbound buffer and then when it gets full, it gets dumped to me all at once. Does that sound right to you?
Would the alternative be to keep track of multiple outbound messages using tcl and a database and just match up each ack as it comes in. It would sure make it difficult to build in any kind of a timeout of the outbound message. Has anyone gone down that path?
- The forum ‘Cloverleaf’ is closed to new topics and replies.