Quote from MikkMmm you missed half the point I think. It's not just that we're not allowed access to random files (which is good to avoid trojans and stuff), it's that we're not allowed outside world communication at any other point in time than login / reload / logout.
Having said that, I wouldn't mind some sort of key:value storage that's more efficient than constructing and parsing Lua - the files could certainly be cached in RAM and read/written to at the usual times. SQL though? I think not.
(And Pasta's argument applies. Addons storing boatloads of data are kinda pushing the boundaries of what Blizzard intends for addons to be doing, so I wouldn't hold my breath for new storage mechanisms.)
Don't think I missed the point, as that was why I said other issues could be worked around with out much effort. A ram overlay with delayed flushes was pretty much what I had in mind when I was writing that as you yourself put. As for SQL... shrug... I used to hate it, but sqlite3 seems lean enough that it still would be more efficient then an lua solution without sql. Of course people would probably do dumb things like forget indecies and such... which is why also mention the isam option which is what I would lean towards myself. I would prefer the sqlite3 option to what we have now though. All in all I think we are in agreement that that a keyed storage system would be a nice alternative to the current SV system.
I am sure it is pushing what they envisioned... between auctioneer, lightheaded and other data driven addons though it does add up to a lot of memory/load time.
Quote from Wintrow2I think you are using a TAD bit too much addons... Or your hardrive is REALLY slow :p.
Probably too many addons, since I am messing with some things lately... but the real issue is, not a slow harddrive, but a network share when one of my harddrives failed I am now using. It seems however they write out the saved variable files is horrid and really shows as such when used like this.