Announcement

Collapse
No announcement yet.

LLP/TCP sender act as server not a client

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • LLP/TCP sender act as server not a client

    We need a LLP/TCP Sender to act as a 'server' instead of a 'client'. We know we can have a LLP/TCP Listener act as either a 'server' or a 'client' - so we need a similar option for a LLP/TCP Sender as well. Or some way of emulating that functionality.

    For example, we need a LLP sender that doesn't initiate the connection to another server, instead it needs to listen on a port and wait for a client to connect. When a client connects, queued messages from the LLP/TCP Sender channel would be sent to that connected client automatically. You could think of it as a web server - but when the client connects, it doesnt make GET or POST requests - the data just goes to the client automatically.

  • #2
    There has been other discussion on this before: http://www.mirthcorp.com/community/f...?t=3818&page=3

    We also have a JIRA issue for it: MIRTH-2446. Please comment on the issue with your specific use-cases. Thanks!
    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

    Nicholas Rupley
    Work: 949-237-6069
    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.


    - How do I foo?
    - You just bar.

    Comment

    Working...
    X