Wiki Page: When recording an AMF3 application why is some of the data in my script Base64-encoded?

If some of the data in a recorded script is Base64-encoded then this indicates that the AMF3 application uses unsupported externalizable traits. Externalizable traits contain the binary representation of an object, an indeterminate number of bytes serialized in an unknown format. The format depends on the class that serializes and deserializes this data. The class also has to know how many bytes it has to consume from the byte stream. SilkPerformer provides support for the three most common classes: flex.messaging.io.ArrayCollection flex.messaging.io.ArrayList flex.messaging.io.ObjectProxy According to Adobe, these three classes are the most common, and are encoded as AMF3. This means that these three classes are parsed like normal arrays or objects, respectively. In case a class other than these three is found, it is assumed that all bytes up to the end of the stream belong to the externalizable traits. The content of such an unknown externalizable trait is stored as Base64-encoded data. An example of this is shown below: qAMKIwEJRFNJZCVEU01lc3NhZ2luZ1ZlcnNpb24GSTE5RjQ5QzYxLUY4MEUt QkE1RS0xQTEyLUQxRTA4OEY5OEZCMAU/8AAAAAAAAAVCcewvONeAAAwhGfSc YfgcGaoyU8fliMYtxQwhGfScYfgvfDUtCsgFjzc1mQIMIZS0VZcYdLCVaSnC 840wX0oA The above example shows that the data is Base64-encoded due to the use of the "DSK" externalizable trait. NOTE : Support for externalizable traits was introduced in SilkPerformer 2008 R2. Old KB# 20698