[MLB-WIRELESS] Elevation maps on BrisMesh site

[Fenn Bailey]

Michael's right on the ball with this - 

There's no reason why a form of image caching couldn't be used. Images
should be generated and linked against a hash of unique identifying
parameters (ie: the node names/locations) and cached. The cache is checked
prior to serving images so slow generation only happens if necessary.

Ideally, this principle should be combined with an aging/freshness mechanism
for pretty much all map image generation.

	Fenn.

> -----Original Message-----
> From: owner-melbwireless at wireless.org.au 
> [mailto:owner-melbwireless at wireless.org.au] On Behalf Of 
> Michael Borthwick
> Sent: Wednesday, 12 January 2005 12:37 PM
> To: Melbourne Wireless
> Subject: Re: [MLB-WIRELESS] Elevation maps on BrisMesh site
> 
> 
> On 12/01/2005, at 11:14 AM, Tom Fifield wrote:
> 
> > It's been on the cards for some time. See 
> > http://www.melbournewireless.org.au/wiki/?LocFinderCrossSections .
> >
> > With regards to the thumbnails, please note that we have 50 
> nodes by 
> > default in the list compared to their 10. In my opinion, as these 
> > images are actually generated dynamically, in addition to the sheer 
> > number of images, node page load times would become a little silly.
> >
> Could they be generated statically as a background process on 
> the server or elsewhere.
> The LOS between two nodes should never change.
> 
> 
> To unsubscribe: send mail to majordomo at wireless.org.au
> with "unsubscribe melbwireless" in the body of the message
> 


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message