
mSLv stands for Mikolaj'S License viewer, or should I rather say license logger/viewer. A thingy I wrote that logs the clearcase (& multisite) licenses and a viewer for the files produced. The first working version was finished in October '02, since then I used it at work for quite some time, and the thing seems to have worked fine. As you will see, the example log files are from that period.
Well, instead of having some uninteresting comma- or whatever- separated format, which efficiently takes little space, I decided to log licenses to much larger and totally space-uneffective XML files. Thanks to this, the license viewer is slowish and the files take much more diskspace than necessary. Ok, that's not exactly the point ;-).
At the time I wrote it, I used msie:download> object to read the log files, but I planned that the time will come that I will rewrite the script using XSLT. Now, after three years the time has come.
The license viewer uses Adobe SVG viewer plugin to plot the licenses. Possibly my approach to using SVG is an abomination, it is however a good abomination of a demo of how to use an abomination of a SVG with an abomination of a javascript.
The javascript is slooow, and probably I would be better off writing something server-side. But I assumed that it would be more useable if the viewer does not have any requirements other than Internet Explorer (it would be a bit of an exaggeration to require a web server just to view a couple of lousy licenses). Maybe I will modify it to work correctly on firefox. I don't know anything else that supports both svg and xslt...
The perl logging thingy, should be scheduled to run every now and then (the viewer truncates to 10 minutes, so it is a good assumption to schedule it every 10 minutes). Frankly, I haven't done much to handle other cases, the user for whom the viewer was (my humble self) did not care too much about that.
The logging thingy creates & modifies the main license file, in which the hyperlinks to the actual log files are stored - one log file for every month. This way the log files do not grow in an uncontrolled manner. With 50 users, the actual files should be no larger than, say 1.5Mb.
I took the real data for the examples. Just that I modified it a bit, changing the maximum number of users, moving the logged data around from some randomly chosen day, removing most of the logs, to make the files lighter (all are < 100Kb). The first file (10.2002) contains the information about the users. So if you want to see the users data, look at data for 10.2002. As you see, I made some generic names for them. In other two files the user information is removed. I altered the log files heavily, so making any assumptions about the licenses, does not make much sense.