<?php
include("sample_utils.php");                    // need to include this to use mk
$mkso = new MKswf_overview("sample01.swf");     // a specific class to read some header data
                                                // default directory is media/flash
$so = $mkso->fetch_assoc();
 
// this is a utility function, ouputs result on browser
$str = trace_array_assoc($so, "<strong>swf header overview</strong>", true, true);
echo show_content($str, basename(__FILE__));
?> 

this is (mostly) the output:

01_getting_swf_overview.php
____swf header overview _______________________
swfFileName: sample01.swf
signature: FWS
swfFileSize: 118
swfInflatedFileSize: 0
swfVersion: 6
isCompressed: no
____end of: swf header overview _______________________

* swfFileSize is in bytes, swfInflatedFileSize applies to compressed swf (CWS signature).

MKswf_overview reads the very first bytes in swf, because they are the only direct data readable, the given info are few an mostly pointless, you may find useful e.g. when you need to quickly browse a group of swf.
To go on reading swf data mk uses serialization, that is assimilate data in memory and then save it in an uncompressed/structured form for future use.
That's the reason why you wil find some temporary data in tmpfolder when using mk.
Some key classes write temporary data and some others read it.