macromedia flash flash remoting: Documentation for FR/.NET states that objects can be passed "back and forth"
between Flash and .NET ("By passing ActionScript objects BACK AND FORTH
[emphasis added] between the remote service and the Flash application, you
can...") I've seen some info on getting objects from .NET into Flash using the
ASObject, but nothing for getting objects from Flash into .NET. The best
workaround, courtesy of mrism, seems to be passing an array into .NET, then
casting it as an ASObject...

Can anyone confirm (MM, are you listening?) that the documentation is wrong
and that, in fact, generic objects themselves CANNOT be passed from Flash into
..NET?

Hi,

As far as I know the only way to pass value objects between .NET and Flash is
to use ASObject. That is however only if you use Flash Remoting MX. FlashORB
however completely removes that limitation. The product automatically adapts
arguments from Flash to the formal arguments types of the invoked methods. The
same thing happen with the return types.

cheers,
Joe

Unfortunately, I've already paid the $$$ for Flash Remoting MX. I've tried
passing a generic object to the .NET class (declaring ASObject as the parameter
type), but get errors. Do you know of any resources I can check out to find
out how to use pass generic objects into .NET? It's just a little frustrating
that the documentation says this is possible, but I've been scouring the Web
looking for a working example and everything seems to be centered on passing
arrays...?

BTW, would it be difficult to adapt existing AS code to work with FlashOrb? Do
you know if they offer a royalty-free version that can be run locally (I've
been developing a local app that presently relies on sockets/Flash Studio Pro
to connect Flash to .NET, because MM limits Remoting to use in a server-client
configuration).

Hi,

I don't know where the confussion is, but yes you can pass objects
between the .NET and flash with the flash remoting. You can pass a
objects like string
object as well as a XML 0bject back and forth. The only limitation i
see is
that both the system should be able to recognize the object passed.

Good Luck

Hemendra Singh Shaktawat

Mndfire Solutions

FlashORB does not require any changes on the client side at all. On the server
side the changes would be mostly to simplif the code. You should be able to get
rid of any references to ASObject (you'd use classes from your application
domain). Also you should be able to get rid of any references to the
server-side Flash component.

As for the version that can run locally, it can do it in the currently release
assuming you have IIS. The upcoming release (1.5) will not require IIS and can
be used as a library bundled into your application.

This looks like a VERY cool product, and the ability to bundle v1.5 with a
local application makes it much more attractive for the projects on which I've
been working. I've already downloaded the trial and look forward to putting
this side-by-side with Flash Remoting once I have time to take advantage of the
trial period.

Any idea when v1.5 (or even a beta) would be available? I'm chin-deep in a
project that relies heavily on Flash Studio Pro and XML sockets to overcome the
limitations of Flash Remoting for local application components. If v1.5 will
be out soon, I might hold off on further development for a chance to save some
money on Flash Studio Pro (which doesn't seem to handle concurrent database
calls very efficiently).

Does Flashorb offer a competitive upgrade by any chance? In any case, this
looks like something that might justify the cost of putting Flash Remoting on
the shelf and replacing it with something that appears to work better for
real-world applications and doesn't impose overly restrictive licensing on the
developer.

Thanks for the tip!