Comments on: Introducing MooTools Cache http://davidwalsh.name/introducing-mootools-cache Legendary scribbles about JavaScript, HTML5, AJAX, PHP, CSS, and ∞. Wed, 23 May 2012 04:02:29 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Tomhttp://davidwalsh.name/introducing-mootools-cache#comment-15056 Tom Wed, 06 Jan 2010 07:15:09 +0000 http://davidwalsh.name/?p=4556#comment-15056 +2Nice class though. It's been so long since I even touched MooTools now after been an early advocate, with all my workplaces insisting on jQuery, it's nice to keep being reminded to check it out again by your blog. +2

Nice class though. It’s been so long since I even touched MooTools now after been an early advocate, with all my workplaces insisting on jQuery, it’s nice to keep being reminded to check it out again by your blog.

]]> By: Alexhttp://davidwalsh.name/introducing-mootools-cache#comment-15049 Alex Tue, 05 Jan 2010 21:58:28 +0000 http://davidwalsh.name/?p=4556#comment-15049 +1 for JSON encoding/decoding +1 for JSON encoding/decoding

]]> By: Sean McArthurhttp://davidwalsh.name/introducing-mootools-cache#comment-15047 Sean McArthur Tue, 05 Jan 2010 20:52:01 +0000 http://davidwalsh.name/?p=4556#comment-15047 You could protect() your private function, instead of keeping a comment about it being private. You could protect() your private function, instead of keeping a comment about it being private.

]]> By: Adriaanhttp://davidwalsh.name/introducing-mootools-cache#comment-15045 Adriaan Tue, 05 Jan 2010 19:06:00 +0000 http://davidwalsh.name/?p=4556#comment-15045 @Chris the Developer: far less likely yes, but still possible...with JSON you're safe. @Chris the Developer: far less likely yes, but still possible…with JSON you’re safe.

]]> By: Chris the Developerhttp://davidwalsh.name/introducing-mootools-cache#comment-15043 Chris the Developer Tue, 05 Jan 2010 18:16:27 +0000 http://davidwalsh.name/?p=4556#comment-15043 @Adriaan - why not use control characters as separators...? \c + \a make great separators, and they are far less likely to appear in a string... @Adriaan – why not use control characters as separators…? \c + \a make great separators, and they are far less likely to appear in a string…

]]> By: David Walshhttp://davidwalsh.name/introducing-mootools-cache#comment-15041 David Walsh Tue, 05 Jan 2010 16:41:59 +0000 http://davidwalsh.name/?p=4556#comment-15041 @Adriaan: Yep, that was where I was hoping I could get some feedback. I think I'll try the JSON encode/decode. @Adriaan: Yep, that was where I was hoping I could get some feedback. I think I’ll try the JSON encode/decode.

]]> By: Adriaanhttp://davidwalsh.name/introducing-mootools-cache#comment-15040 Adriaan Tue, 05 Jan 2010 16:37:04 +0000 http://davidwalsh.name/?p=4556#comment-15040 The problem with string separators are that there's always a chance that they might actually occur in a value...which will then corrupt the data. The problem with string separators are that there’s always a chance that they might actually occur in a value…which will then corrupt the data.

]]> By: Chris the Developerhttp://davidwalsh.name/introducing-mootools-cache#comment-15039 Chris the Developer Tue, 05 Jan 2010 16:21:42 +0000 http://davidwalsh.name/?p=4556#comment-15039 Another argument for extending Hash.Cookie is that your class requires the developer to cache.save() whereas the values are saved immediately with Hash.Cookie... Another argument for extending Hash.Cookie is that your class requires the developer to cache.save() whereas the values are saved immediately with Hash.Cookie…

]]> By: thomasdhttp://davidwalsh.name/introducing-mootools-cache#comment-15038 thomasd Tue, 05 Jan 2010 16:17:46 +0000 http://davidwalsh.name/?p=4556#comment-15038 @David Walsh: I see your point when saving the value as an object, but if you use JSON to save the value as an array, you even save some characters: Example using your sep: key:://::hello world:://::123456:://::60:://::myfuncExample using JSON to encode an array: ["key","hello world",123456,60,"myfunc"]And you still just need one function call (JSON.decode) to get an full functional JS-Array. And withJSON.decode(jsonified_string).associate(["key", "value", "expires", "duration", "fn"]);you have the full object back again, all without using the Hash-Native. @David Walsh: I see your point when saving the value as an object, but if you use JSON to save the value as an array, you even save some characters:
Example using your sep:
key:://::hello world:://::123456:://::60:://::myfunc

Example using JSON to encode an array:
["key","hello world",123456,60,"myfunc"]

And you still just need one function call (JSON.decode) to get an full functional JS-Array. And with

JSON.decode(jsonified_string).associate(["key", "value", "expires", "duration", "fn"]);

you have the full object back again, all without using the Hash-Native.

]]> By: Nickolas Simardhttp://davidwalsh.name/introducing-mootools-cache#comment-15037 Nickolas Simard Tue, 05 Jan 2010 15:57:49 +0000 http://davidwalsh.name/?p=4556#comment-15037 Interesting concept. It may even make cache and cookie managing easier... I wish I had more time to read the code entirely, but I shall do that later...Until then, keep up the good work. Interesting concept. It may even make cache and cookie managing easier… I wish I had more time to read the code entirely, but I shall do that later…

Until then, keep up the good work.

]]>