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: Joel Dillon <emily#cornholio,new.ox.ac.uk>
- Date: Mon, 27 Apr 1998 11:24:42 +0100 (BST)
- Delivery-date: Fri Apr 27 03:25:34 1998
- Delivery-date: Fri, 27 Apr 1998 03:25:34 -0700
- Envelope-to: claw#kanga,nu
- Reply-To: mud-dev#kanga,nu
- Sender: "Petidomo List Agent,,,," <petidomo#kanga,nu>
On Mon, 27 Apr 1998, Justin McKinnerney wrote:
> >
> > Well, at work we handle persistence in applets by passing them their
> > identity (the name of their user or whatever) via an applet parameter and
> > sucking data from a server over a socket or jdbc connection. That's good
> > enough for our virtual conferencing system and presumably it'd be good
> > enough for a mud client as well.
> >
> > Jo
>
> 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.
Jo
--
MUD-Dev: Advancing an unrealised future.
- Thread context:
- [MUD-Dev] Re: (fwd) AD: [custom graphical] whitestar Crossfire MUD, (continued)
[ Other Periods
| Other mailing lists
| Search
]