Crossfire Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CF: images & caching.



>  The real issue/discussion seems to be coming down on how to handle client
initialization that wants to verify it has all the images before doing anything
else.


	Hmm. Why not have each image archive have a verion number? Have
	"blessed" image and map archives that have version numbers stamped
	on them. So this way, server powers up, loads the first map (city
	map) from the archive and reads in the image archive version needed.

	When a client logs in, the server and client swap image archive 
	version numbers. If they dont match, the server can either
	1) warn the client and proceed normally, or 2) refuse connection
	until the client gets the proper image cache version or 3) 
	transmitts the differences to the client.

	Since, as you point out, the ordering of the images can change,
	option 3 seems pretty icky, considering *every* needed image would
	then have to be transmitted (and bandwidth out the window :P ).
	This is especially true if from one version to the next, an
	early image is removed, and all the ordering has changed. (BTW,
	how do you detect that??).

	
							-b.t.

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