Flash remoting was our first, sort of formal take at connecting the J2EE and enterprise world to Flash. Flash contains a mechanism for asynchronously receiving XML data and html data, but it wasn't particularly easy to use for most developers of Flash and it also didn't expose server side resources in a way that developers wanted them to be exposed. So what Flash remoting does is it provides a script-based API for invoking methods on services. Those services could be implemented as stateless session façade using Enterprise JavaBeans, they could be JMX MBeans, they could be JavaBeans or Java classes. The client-side developer sees simply an API in which there's a service exposed and it has functions available on it and they can asynchronously invoke those functions. So Flash Remoting provides our first means for really easily connecting Flash components to J2EE resources. We also do a version for ColdFusion so that we can use the exact same APIs to hook Flash up to ColdFusion and we do a version for .NET as well so a number of .NET resources can be connected all using the same API.