> If you're getting it through an object-serialization framework (AMF, etc.),
Yup, that's what I'm doing. > then you may be receiving it already as a ByteArray, in which case you need to load it with a Loader instance. Where could I find information about this? I've found the flex documentation on these back-end/front-end integration issues rather thin on the ground. Cheers, David. --- In flexcoders@yahoogroups.com, "Troy Gilbert" <[EMAIL PROTECTED]> wrote: > > > When the employee objects are sent back to the client I don't know how > > to bind to this property as <mx:Image source="..."/> takes the > > *location* of the image, not the binaries themselves. > > Depends on how the data (or what format) its arriving in to your Flex > app. If it comes over the wire in an XML doc (like a BASE64 encoded > BLOB from a database), then you'll need to turn that into a ByteArray > (I believe AS3 corelib, from Adobe -- see Google code -- has API for > this), then load the ByteArray (assuming its the bytes of a > PNG/JPG/GIF/SWF) with the Loader class. > > If you're getting it through an object-serialization framework (AMF, > etc.), then you may be receiving it already as a ByteArray, in which > case you need to load it with a Loader instance. > > Note, when using Loader, if you have it load bytes from a ByteArray > there is still a one-frame delay before the loader completes, i.e. you > do have to wait for it to fire the COMPLETE event before the content > is accessible. > > Troy. >
