Thanks Ryan, i understood..
On 28 May 2013 00:59, Ryan Ternier <ryan.tern...@cgi.com> wrote:
> vijayaratha vijayasingam <vijayaratha@...> writes:
>
> >
> > Hi all;Currently, my initiator and acceptor applications communicates
> sequentially..Can i make that as asynchronous process?
> > What i mean is, when my initiator application thread sends request to the
> backend application, it has to wait for the response from backend. I would
> like to make that as asynchronous? Is that right? or is it against the HL7
> protocol?
> >
> > Thanks
> > -ratha
> >
> >
> >
> --------------------------------------------------------------------------
> ----
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring
> service
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_may
> >
> >
> --------------------------------------------------------------------------
> ----
> > Try New Relic Now & We'll Send You this Cool Shirt
> > New Relic is the only SaaS-based application performance monitoring
> service
> > that delivers powerful full stack analytics. Optimize and monitor your
> > browser, app, & servers with just a few lines of code. Try New Relic
> > and get this awesome Nerd Life shirt!
> http://p.sf.net/sfu/newrelic_d2d_may
>
> That isn't against HL7. How HL7 is implemented is based off the business
> rules of the organization.
>
> For example, let's take a Health Authority / Hospital.
>
> When they do an initial lookup using your Health #, they'll want that
> transaction to be synchronous. It should be fast. The same if they want to
> add a new person and get back an ID, or do a search.
>
> However, let's say they want to update someone, or merge. Those
> transactions
> can be thrown to an asynchronous method because they don't need the results
> back right away. In these cases you will need to have a ACK/WAK/NAK sent
> back - which is synchronous, however there would be an asynchronous layer
> that processes the message and sends back the result to a specific end
> point.
>
> Hope that helps somewhat.
>
>
> /RT
>
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
> _______________________________________________
> Hl7api-devel mailing list
> Hl7api-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/hl7api-devel
>
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
_______________________________________________
Hl7api-devel mailing list
Hl7api-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hl7api-devel
