Hello, >> People interact with the (remote) application by means of the terminal >> emulator. Things get sent to/from the printer based on escape sequences >> initiated by the application. >> >> In the original (proprietary) application, the dispatching functionality >> is integrated in the terminal emulator, so it is understandable that >> pheoebus phoebus wants to keep that structure in the replacement.
I want to emphasize that your response reflects a clear understanding of our specific needs and the constraints we are facing in this project. >> I proposed splitting off the "mux" functionality from the terminal >> emulator functionality, but I fully understand that phoebus phoebus >> favours the more "conservative" approach. The use of a terminal emulator in passthrough mode is tied to our existing infrastructure and the way our application was originally designed. Within the scope of the ongoing project, which involves migrating our application from Unix to Linux, it is not within the migration's scope to alter this particular aspect, as it is both critical and sensitive. While I have some leeway to propose technical enhancements and changes, this specific area is off-limits due to its significant impact on a crucial functional aspect from both a business perspective and certain certification standards under which our POS system is certified. >> By the way -- back then (TM), when terminals were real things, it was >> not unheard of that they came with an attached printer and some bar >> code scannery -- all handily multiplexed over the RS-232 (or something >> more monstruous), orchestrated via intricate escapery. Yes, that's indeed how it used to work. In our case, the complex escapery you mentioned, for instance, involves the printing process using the ESC/POS printer control language. >> So the thing is just a natural evolution dating back to The Dinosaurs. While it may seem unusual and archaic by today's standards, this approach has proven to be an effective solution for addressing the needs of our business. It has been thoughtfully evaluated and retained because it ensures the efficient execution of our application while aligning with our business requirements. Just like certain evolutionary traits persist over time in the process of Darwinism, this approach endures, indicating that the choice isn't as misguided as it may appear. Regards, Thierry
