Crossfire Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: CF: images & caching.
> On Mar 9, 7:21pm, Brian Thomas wrote:
>>
>> Here's a semi-naive question: Why dont we identify the images
>> by their names instead of their (compiled) numerical position?
>> In such a case, you could arbitarily add images to any cache
>> without screwing up the prior identification of other images.
>
> When doing map updates, it is much more efficient to send what is on a
> particular space by image number (2 bytes, although I believe the current
> packing actually gives something less than that, but still enough for current
> terms).
>
> If you use image names when dealing with transmitting that, map transmission
> size greatly increases.
>
> As a note - when using image caching the server will send the name & number
> for images, so the client can do the translation - this is also why the client
> stores the image in teh cache via name, so when it does the lookup, it does it
> via name.
As servers can have differing images due to differences in maps and are
likely to have different image numbering schemes then it appears that part
of the client server initialization must includes the server sending the
client the complete list of image number and it's image name. Otherwise
the client image cache would show the wrong images if connected to a server
with different maps than client's previous server.
It should be noted that a client caching images and connecting to different
servers would likely end up with more images than exist on any individual
server. That is not a problem, it just demonstrates the requirement
that server sends client the number to name mapping to be used for this
session.
sdw
[to unsubscribe etc., send mail to crossfire-request@ifi.uio.no]