> Nicolas, > > You're right mx.remoting classes are free, but not open source, but > there's another implemementation of remoting client classes in > ActionStep package. Those classes could be ported. I never use them, but > I read a while ago, about it and think this classes could be used > without the whole ActionStep framework, if some ActionStep experienced > developer could confirm that... > > Best, > > C.
Yes, after looking a bit into it, it seems that mx.remoting is "just" providing some highlevel wrapper for the standard class NetConnection, with additional debugging services (by establishing a LocalConnection to log into the separate NetConnectionDebugger ?). The NetConnection class is available in haXe so it means you can do AMF-based Remoting from haXe right now, although building a bit more structured API like the "mx" package is providing would make some sense. One interesting possibility would be to actually wrap the NetConnection as an haXe AsyncConnection, so this way you could transparently use either standard haXe Remoting or AMF-based Remoting by just using a different AsyncConnection contructor. Remoting is not a term specific to Flash, it's used by other technologies as well, some older (Corba) or more recent (.NET), simply Google for Remoting and match the results. The principles of both haXe Remoting and AMF Remoting are the same. The only difference is the underlying protocol used to communicate between the client and the server, and the capabilities of Data serialization. That's why I clearly make the difference between "haXe" Remoting and "AMF" Remoting. Nicolas _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
