There are several ways to solve this problem, and the sototon depends on the architecture of the system (resolution, availability) and knowledge for its implementation.
Basically, these are parameters that are affected by these factors:
- print directly from the paste application or a notification from the paste application: can you change this application? Is it possible to contact the print application from this application? (It can be implemented, for example, with WCF)
- sql dependencies (SQL notification request) : the print application must create and subscribe to the sql dependency: do you have permission to create dependencies on the server?
- poll: quick and dirty solution: use the "timer" to check if there is new data and print it when it is available.
The last solution is one that will pose the least problems. It is not smart, but very easy to implement. You can adjust the polling period depending on the expected number of messages and the "real-time" requirements of the pringing application.
source share