I've not yet experimented with mirroring. Its our busiest time of the year here, but that doesn't stop you thinking about the future.

We are a small company running 24/7 and external out of hours support is expensive (2am on sunday morning is !!) so we stuck with win10 because it's what we know, what we can fix quickly. Not the best OS, but we do know where we are with it.

It's where we have to go and play, but just wondered.


does cache have to be the unicode version or can we use nodeJS with "standard cache" (I'm using nodejS 4.2.1 in a windows environment with 2016.1 cache)

the reason I ask, I have installed the nodeJS (64bit) and it's fully working with the unicode version of cache (I read that I should be using unicode somewhere) but when I try to copy the same setup into 32bit windows environment (NON unicode) making sure I have the 32bit nodeJS, it won't connect,

Been through loads of things, but its only unicode/non-unicode that seems to be different

Daimor on github gave a very useful set of classes (I believe v2015 onwards) that allowed you to log anything and everything to a class


you can pass in event types such as NONE,FATAL,ERROR,WARN, INFO,STAT,DEBUG,RAW and then it will handle just about anything,  objects, strings, lists etc and then just do sql's for the actual messages

Timur:  I originally took my code from Introducing new JSON capabilities in Cache 2016.1 article  on this website and having not played with the new json capabilities, started with this method.

the answers  comments clearly show there are many ways to write the same thing.

Stefan: I prefer legibility over brevity. and your solution does indeed help me visualise the end output. So my preferences is to adopt this version.

thanks for the answers.
Any other comments ?