Re: [HAPI-devel] Fwd: HL7 ack message control

2013-04-23 Thread vijayaratha vijayasingam
Thanks christian..i got it.. Rgds, -ratha. On 23 April 2013 17:30, Christian Ohr wrote: > No, fire-and-forget basically means that the client does not care about > the kind of ACK it gets back. > In Hl7 control you always get back a response and you are supposed to wait > for the response, too

Re: [HAPI-devel] Fwd: HL7 ack message control

2013-04-23 Thread Christian Ohr
No, fire-and-forget basically means that the client does not care about the kind of ACK it gets back. In Hl7 control you always get back a response and you are supposed to wait for the response, too, before sending the next message. Otherwise the behavior can be unpredictable and depends on the mul

[HAPI-devel] Fwd: HL7 ack message control

2013-04-23 Thread vijayaratha vijayasingam
Hi christian; Thanks for your quick and clear response; One more question; "Often, messages are sent in a fire-and-forget mode, and clients are only maybe interested if the message has been received rather than how they are processed and what the result is. " I have written myclient like this; I

Re: [HAPI-devel] Controlling autoack message..

2013-04-23 Thread vijayaratha vijayasingam
Sorry ignore this thread, half written..i sent another query.. On 23 April 2013 14:41, vijayaratha vijayasingam wrote: > Hi all; > Im new to hl7 technology, > What im trying is; > I receive a request from the clint, and my application process it sends an > auto ack/nack message to client. > > My

[HAPI-devel] HL7 ack message control

2013-04-23 Thread vijayaratha vijayasingam
Hi all; Im new to HL7 technology, bear me if im wrong.. Currently i can send and receive auto ack/nack message from client. My client is like this; Initiator initiator = connection.getInitiator(); HL7Message sampleMessage = new HL7Message(); //send Message response =

[HAPI-devel] Controlling autoack message..

2013-04-23 Thread vijayaratha vijayasingam
Hi all; Im new to hl7 technology, What im trying is; I receive a request from the clint, and my application process it sends an auto ack/nack message to client. My client code is like; -- Try New Relic Now & We'll Send You