MUD-Dev
mailing list archive
[ Other Periods
| Other mailing lists
| Search
]
Date:
[ Previous
| Next
]
Thread:
[ Previous
| Next
]
Index:
[ Author
| Date
| Thread
]
[MUD-Dev] Re: Java for Mud Client (Crossfire MUD topic)
- To: mud-dev#kanga,nu
- Subject: [MUD-Dev] Re: Java for Mud Client (Crossfire MUD topic)
- From: J C Lawrence <claw#under,engr.sgi.com>
- Date: Wed, 29 Apr 1998 17:04:54 -0700
- Delivery-date: Wed Apr 29 17:05:46 1998
- Delivery-date: Wed, 29 Apr 1998 17:05:46 -0700
- Envelope-to: claw#kanga,nu
- Reply-To: mud-dev#kanga,nu
- Sender: "Petidomo List Agent,,,," <petidomo#kanga,nu>
On Mon, 27 Apr 1998 11:24:42 +0100 (BST)
Joel Dillon<emily#cornholio,new.ox.ac.uk> wrote:
> On Mon, 27 Apr 1998, Justin McKinnerney wrote:
>> The issue was download time for graphics in the java client if it
>> were applet based - so the persistance required here is local
>> storage of applet data so a user doesn't have to download it every
>> time.
> Ah *bopme* Perhaps one way (not a very nice way) would be to
> encode the data as constants in the class files. That way the
> browser would cache them for you; but you wouldn't want to do that
> for large amounts of data. run into problems with older browsers.
Umm...user programmed objects? How about doing a Tiny-* clan or
LambdaMOO-style approach where the entire world is user-written and
potentially dynamic self-modifying code...
--
J C Lawrence Internet: claw#null,net
(Contractor) Internet: coder#ibm,net
---------(*) Internet: claw#under,engr.sgi.com
...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...
--
MUD-Dev: Advancing an unrealised future.
- Thread context:
- [MUD-Dev] Re: Java for Mud Client (Crossfire MUD topic), (continued)
[ Other Periods
| Other mailing lists
| Search
]