CF: Images and Caching

To: CrossFire Mailing List <crossfire@ifi.uio.no>
Subject: CF: Images and Caching
From: Kristofer Bosland <krisb@ring.org>
Date: Tue, 10 Mar 1998 11:49:52 -0800 (PST)
Sender: owner-crossfire@ifi.uio.no


	I have some ideas here:

1. Common case: you run again and again on the same server, with the same
images

2. Incremental updates are desirable

	It seems to me that a good method would be a hierarchical checksum
scheme.  For each image file, you have a name and a checksum, and maybe a
version.  No too much overhead (<100bytes) with very good identification.
Then, you have a images list, which also has a checksum and maybe a
version.  This is maybe 50k.  Then your interaction is:

client: send me your image set id
server: (100 byte id: .1s)
client: I don't have that set, send me the details
   to user: Please wait for image loading
server: (50k set: 10-30s)
client: OK, images 1, 357, and 666 are new, send me those
server: (3 images @ 5k each: 5s)

	This scheme should be trouble free, and fast in the common case.
For even more efficiency with a little more complexity, break the image
list into smaller chunks, such as every 5K or land/creatures/items/?

-Kris

[to unsubscribe etc., send mail to crossfire-request@ifi.uio.no]

Prev by Date: CF: pupland raffle2_u3?
Next by Date: CF: client image loadiing
Prev by thread: Re: CF: a question on pixmaps
Next by thread: CF: pupland raffle2_u3?
Index(es):
- Main
- Thread