Hello, >> I don't understand why you involve a terminal emulator in the process. >> Do you need to see the data that goes through the COM port displayed in a terminal (like minicom)?
The existing solution is designed in that manner. We migrated our application from AIX to Linux, and this is the approach that has been historically used. On the client-side, we are exploring if there's an open-source alternative to the proprietary solution that fulfills the necessary functions. >> I do not understand what you are trying to do at all. Are you trying >> to print to a remote printer that has a serial port? For that, >> perhaps you could use a printserver with a serial port (if you can >> find one) or a printserver and an adapter from parallel to serial. In our POS system, the printer is located at the POS station so that our customers can have their prints quickly and in front of them. Printing from the server in this POS context doesn't make sense for us in this scenario. >> If you're trying to create a two-way communication between a remote >> server and a remote client, with the client sending and receiving the >> data through its COM port (for some weird reason), you could do that >> over ethernet, using your own protocol or an existing one (maybe even >> xmpp). We already utilize the TCP protocol for communication over Ethernet, as the transparent printing flow is encapsulated within the encrypted SSH stream. Depending on the ASCII control codes, the data either displays on the terminal screen or gets printed on the connected printer. So, we are already leveraging Ethernet and TCP for this purpose. >>Unfortunately, COM ports have become quite rare :( In the retail environment, COM ports are still quite common, especially in equipment such as POS printers. Regards, Thierry
