When I went to Queen's University, the web app for course registration, viewing your marks and other related tasks was rumoured to be a wrapper around a telnet

When I went to Queen's University, the web app for course registration, viewing your marks and other related tasks was rumoured to be a wrapper around a telnet interface. I never got confirmation, but the following evidence was enough for me: - Fixed number of columns/rows output on a given page and rendered in a fixed-width font so things would align. - The need to navigate through "pages" of information that were far smaller than what a browser could handle, but would make sense in a terminal window. - A form-driven interface with buttons for separate actions; the buttons seemingly would map to certain keypresses in a terminal interface. I'm guessing the original computer-based system provided a telnet interface in the '90s but this was deemed insecure/out of date as the years went by. Not wanting to significantly change the architecture, a web wrapper must have been deemed the best option.