so this guy came out with an AJAX client and its awesome, you can literally use any browser without having to have telnet, or flash, or open ports etc. this is ideal for work! but i cant find any info about the guy who made it and was wondering if anyone knew him? I would love to be able to use his source!
There are several utilities like this out there. Someone just posted about setting up an AnyTerm-based one just a couple weeks ago.
Essentially, all these utilities do is run a proxy daemon that connects to the MUD and keeps an open connection to it. It then uses regular HTTP/AJAX calls to retrieve and post I/O to this proxy daemon. Using Python or Ruby or the like, whipping together such a daemon is almost trivial. Getting the CSS/JS to display a good terminal using HTML is probably the trickiest part of all, honestly.
I've been toying with a similar idea for a while. A ZMP-enabled proxy could allow for a very intricate client, with all the paper dolls and automappers and so on I could ever want. If the client-side JS is modularized correctly, it would even be possible to slap in network connections via Flash/Silverlight/Java to avoid the overhead of AJAX through a proxy (mostly the cost of the request, response, and possibly reconnect cycles HTTP imposes) or even through a browser-native connection once WebSockets or some variant finally gets into a browser.
Hey Crat, i see how you used that on your test-mud. i like it allot. I have a linux server and was wondering if i needed admin rights to be able to install / run "AnyTerm"? The reason i ask is i do not have that since its a rented server.
Hey Crat, i see how you used that on your test-mud. i like it allot. I have a linux server and was wondering if i needed admin rights to be able to install / run "AnyTerm"? The reason i ask is i do not have that since its a rented server
Technically you do not need to be root to run and test anyterm. It's worth playing around with as a user, to get an idea of it. It can run as an internet-facing daemon.
However, it is mostly intended to be run behind an apache proxying configuration, and as such, you'd need to have access to your apache config files, as well as privileges to start/stop it.
Remember to be super careful, and read through all the docs. Doing it wrong can lead to major security exposure.