On Thu, Feb 14, 2008, Michelle Konzack wrote: > Am 2008-02-13 10:25:32, schrieb Matus UHLAR - fantomas: > > by using the same URI? or by different URI each time a song is requested? > > each of this makes problems with HTTP caching... > > Yes, it is always the same url... > > For example: The original file is sampled in 192kBit and then a user > use: > > <http://musicserver/?rate=64&name=how_to_get_gnump3d_caching.mp3> > > which would resample the file to 64 kBit, but requesting the same file > 10 times, result in 10 different files... > > The resamlpling is NEVER the same... (checked with md5sum) Why not? > I the only thing I can imagine is, that I write a gnump3d patch, which > copies the resampled file into a cache directory, which can be in a > ramdisk, and then the next time someone is requesting the same URL, > gnump3d is looking first into the cache and if it is there, it use it > and otherwise it resample the file. I'd do something like that on disk. You may even find you're able to make more effective use of the buffer cache that way. Adrian
