I'm not entirely sure what you mean with "message aggregation". Do you
intend to correlate subsequent messages referring to the same patient
and execute some sort of combined logic?
Objects of type Application are completely unaware of the server
object that forwards a Hl7 message. So, yes, assumi
Our approach is a bit different. Our logic is completely decoupled which
allows us simply to run multiple instances of the same process having
different ports. Could this perhaps be a valid solution for you?
PS @ Laurent - is there any reason why you don't use the
ca.uhn.hl7v2.llp.ExtendedMinLower
Our issue is a bit different. We used to process an aggregated feed, so
we have smart logic that can already process a variety of feeds
intelligently with our handler. Running 2 instances of the server would
work but would not perform well enough as we do not have a multi-process
caching strate
Are there any objections to simply use two instances of SimpleServer
using the two different ports you mentioned?
Christian
2012/12/17 Brijesh Singh :
> Hi - As per HAPI documentation, messages can be processed through HAPI using
> SimpleServer on a port. We have a requirement where data coming f
We have written several programs which implement simple server on different
ports and run them separately. This enables us to log each feed and stop/start
them individually when required. Whilst it can mean you end up with quite a few
processes running, it has proved an effective technique.
Ia
Hi - As per HAPI documentation, messages can be processed through HAPI
using *SimpleServer * on a port. We have a requirement where data coming
from different feeds to our application on different ports. Does HAPI
provide API to handle incoming messages on different ports? All these feeds
are inbou
6 matches
Mail list logo
