Just a couple of questions...
On Thu, 8 Jul 1999, Jeffrey Margolis wrote:
> Hello again.
> Well today when i got home from summer school, i started thinking. (I
> know it doesnt happen that often but bear with me) A while ago i posted to
> the list about maybe writing a little protocal for which a client could
> communicate to the mud and create a nice front end for immortals. Well that
> suggestion included a small example of a somewhat simple protocal (it updated
> a player list in the client) when i realized why bother creating something so
> large? Is it worth it? Or is there a better way.
What do you intend to have immortals do from this interface? Why is this
better than just logging in?
> My new idea is that maybe the client could actually be a program that
> connects to the mud and recieves minimal information from the mud. The
> actuall control would be web pages that are dynamicly updated (by the mud) as
> the data changes (like the who list in HTML). Throw that together with a
> little javascript (maybe with a perl scriptthat would run the autorun) and
> add a web browser control that will automaticly reload the page when a
> message like ##UPDATE is sent from the mud (Notioce how considerably less is
> sent as to my old idea) and you have yourtself a pretty nice frontend. Well
> that is what i think at least.
The question I have here, is who does the mud send stuff to? Like this
##UPDATE command - where is this command sent, and what is listening for
it? You mention a perl script - do you intend to log in to the mud with
this perl script to receive messages? I guess you could conceivably use
server push to have a cgi script send updated static pages to the
immortals' browsers by keeping track of the last modified times of all of
these automatically generated pages, and pushing them when the date
changes...
> I am just curious what you think of thi, and if i did make this, would anyof
> you out there be interested in it. This way you can also make additions to
> the services supplied by the fropnt end with out recompiling the whole client.
I'm still not sure what you'd use it for. At best it could be used to
look at stuff. Without some sort of timestamping, you wouldn't really
have any way to know how stale that data is that you're looking at... If
you want anything close to real time updates, you're probably better off
having the mud listen on another port, and connect there with an applet.
This way you might be able to send in commands, not just monitor activity.
> Well talk toy you later, and as always send all complaints (about this
> particular e-mail) to cool20@aol.com
>
> -Jeff
>
Eric
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST