2006/5/16, erix tekila <[EMAIL PROTECTED]>:
Totaly agree, Remoting for a lot of us makes think about "AMF". I'll rename to haXe RPC or something like that as erix points.
AMF needs the mx.remoting classes which I haven't used up to now and arenot OpenSource. That's one of the reason why I cameup with haXe Remoting
which permit to send datas but also classes instances over any kind of
connection (ExternalInterface, XMLSocket, HTTP), either synchronously or
asynchronously depending on what is possible.
You shouldn't call it remoting.
It confused me also.
haxe-RPC suit more on it.
Totaly agree, Remoting for a lot of us makes think about "AMF". I'll rename to haXe RPC or something like that as erix points.
As for haXe AMF Remoting, what I see are theses two possibilities :
a) port theses classes to haXe and use them for haXe-AMF-Remoting. It
has some restrictions since the mx.remoting sources belongs to Adobe.
b) comeup with an OpenSource implementation of mx.remoting that could be
directly integrated in haXe distribution.
Correct me, but don't pixlib, aswing and actionstep support amf remoting ?
The (b) might be of some interest for Red5 people since having an
OpenSource Remoting server would make much sense if these is a
client-side OpenSource API as well. What are the plans
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
--
::| Carlos Rovira
::| http://www.carlosrovira.com
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
