ThreadBoard ArchivesSite FeaturesActiveworlds SupportHistoric Archives |
dump cache (Wishlist)
dump cache // WishlistbowenMay 3, 2003, 4:35am
I want this above all else, a dump cache button on the toolbar. (say
there's a mode you can switch into... like developer mode) --Bowen-- bowenMay 3, 2003, 5:12am
[View Quote]
Hey, if we're getting technical... why not the ability to "reload" the
object. Just place a little icon on the build dialog to reload it. Oh how happy I'd be. -- --Bowen-- technozeusMay 19, 2003, 3:58pm
A long time ago, I suggested adding the ability to set a date and time before which any cached items would be considered out-dated, forcing the Active Worlds browser to check for newer versions of them. Would this serve the purpose you're talking about?
For example, if you upload a new file that you want everyone to have, you could simply click a button in the World Features dialog to set the current time and date as the earliest time and date any cached file can have been last checked for updates on without having to be checked again. This would augment the Object Refresh Rate, as it would allow a way to make sure that all objects in the cache are up to date for all visitors to a world, without having to force all cached files to be re-checked every time the person re-enters the wolrd as setting the Object Refresh Rate to 0 does. TechnoZeus [View Quote] bowenMay 19, 2003, 4:40pm
[View Quote]
It wouldn't be the same. And good lord man, wrap your text. I had to
rewrap it because I couldn't read it. -- --Bowen-- technozeusMay 19, 2003, 5:26pm
Not all newsreaders lack the ability to auto-wrap text when it is displayed. I leave it unwrapped intentionally, because otherwise it tends to get wrapped and re-wrapped, and end up with every other line having only a word or two on it. It also avoids certain complications like having example text split places it shouldn't have been split.
Anyway, no it would not be the same. THere is a distinct difference between a button in the "build dialog" (where ever that is) to reload an object, and a setting which would all objects, textures, sounds, avatars, and avatar animation sequences which haven't been checked for updates since a certain time and date to be checked for new updates automatically as soon as they are needed. TechnoZeus [View Quote] bowenMay 19, 2003, 5:32pm
[View Quote]
That's why you snip posts, and not leave it FUBARd.
> Anyway, no it would not be the same. THere is a distinct difference > between a button in the "build dialog" (where ever that is) to reload > an object, and a setting which would all objects, textures, sounds, > avatars, and avatar animation sequences which haven't been checked > for updates since a certain time and date to be checked for new > updates automatically as soon as they are needed. Well, it needs to be a button as well, simply for a developer's sake. Doing options is such a pain. Not only that, not every person who has the ability to build, and upload to the OP, has CT. -- --Bowen-- codewarriorJul 7, 2003, 2:26am
Better cache management would definitely make me a lot happier.
The per-object reload button is a great idea when you are building, although it won't help people who visited your world before the object changed and who come back later. I doubt if AW is going to add a last changed date to every object in your world on their server and then send that down the pipe to the browser of everyone who comes to visit. The 'last modified date' suggestion by TechnoZeus is probably more along the lines of being doable without major chunks of stuff being rewritten. I would be happy enough with something like that. Setting the object refresh to one miunute while your are developing a world is a horrid kluge, and again it doesn't help when someone came and visited, then comes back later after you are all done. I really want a 'last nuked on' date I can set so no matter when someone comes to visit me, their browser can tell right away that the entire cache should be flushed. What I would actually prefer though is that it be a special file that is loaded from my OP like the avatars.dat file is, since that way server side cleverness can invalidate some peoples caches and not others.It could even just be a file that is simply checked for it's date.. not actually read and interpreted. This would be useful to implement a content system where a visitor sees a certain set of textures and objects before they 'sign up' through some mechanism outisde of AW. A server script can then recognize that they need to flush these 'non member' objects from their cache and get the 'real ones'. Dynamic server side content in AW is possible, and it's a lot of fun to play with, but with no cache management mechanisms available to developers it is a complete dead end. It's a shame too because all that is really needed is a way for the server to completely invalidate it on a per user basis. [View Quote] |
