Fixed issue #2 but CCSO is now handled the same way that telnet is as…

… CCSO would required its very own client
jankammerath · Nov 26, 2019 · d5187f2 · d5187f2
1 parent 9e9c853
commit d5187f2
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 0 deletions.
diff --git a/build/Gophie.jar b/build/Gophie.jar
diff --git a/src/org/gophie/ui/MainWindow.java b/src/org/gophie/ui/MainWindow.java
@@ -279,6 +279,16 @@ public void searchRequested(String text) {
                         }
                     });
                     break;
+                case CCSCO_NAMESERVER:
+                    /* CCSO is not part of the Gopher protocol, but its very own
+                        protocol and apart from floodgap.com's CCSO server there
+                        is hardly any server to test interaction with. The CCSO
+                        protocol can also be considered quite simple. A CCSO client
+                        would be a software of its own, but sources are even fewer
+                        than Gopher servers out there. Hence, Gophie allows the
+                        user to use CCSO servers throgh their Telnet client. */
+                    this.openTelnetSession(item.getHostName(), item.getPortNumber());
+                    break;
                 case TELNET:
                     /* handle telnet session requests */
                     this.openTelnetSession(item.getHostName(), item.getPortNumber());