Depending on how your console functions, I'd have expected something more
like:
PID|||123456||Doe^Johnstem200701011539||ADT^A01^ADT A01123
But at any rate, try adding this before the println:
encodedMessage = encodedMessage.replaceAll("\r", "\n");
Jere
useful to happen when that timeout is hit.
I think the most reasonable thing is to treat it as fatal and close the
connection. For example, if you don't want ill-behaving clients to cause
you to leave sockets open for ever.
Jeremy Huiskamp | karoshealth
Software Engineer
7 Father David Bauer
ified that something actually happens when you hit your
timeout? Maybe I'm missing something...
Jeremy Huiskamp | karoshealth
Software Engineer
7 Father David Bauer Drive, Suite 201
Waterloo, ON, N2L 0A2, Canada
www.karoshealth.com
On 15 March 2016 at 04:00, Martin Schlapfer
wrote:
&
Anyone have any thoughts on the below question?
Thanks,
Jeremy Huiskamp | karoshealth
Software Engineer
7 Father David Bauer Drive, Suite 201
Waterloo, ON, N2L 0A2, Canada
www.karoshealth.com
On 14 September 2015 at 23:32, Jeremy Huiskamp <
jeremy.huisk...@karoshealth.com> wrote:
&g
\n"));
Which produces:
MSH|^~\&|20151217123953.819+0100||ORR^O02^ORR_O02|210835|P|2.5
MSH|^~\&|20151217123953.819+0100||ORR^O02|210835|P|2.5
Jeremy Huiskamp | karoshealth
Software Engineer
7 Father David Bauer Drive, Suite 201
Waterloo, ON, N2L 0A2, Canada
www.karoshealth.com
On
want some feedback first. Would
it be acceptable to close the connection when a SocketTimeoutException
happens? Are there legitimate use cases for triggering and then recovering
from a timeout?
Jeremy Huiskamp | karoshealth
Software Engineer
7 Father David Bauer Drive, Suite 201
Waterloo, ON, N2L 0
6 matches
Mail list logo
