[haXe] Red5/FMS and Haxe platform

[Marcelo de Moraes Serpa]

Hi Nicolas, thanks for the explanation :)

>Now if you want to replace your haXe/Flash client by a haXe/Neko one,
>ou will have to manually connect using a neko.net.Socket and manage the
>RTMP protocol by-hand.

You mean I would have to actually implement the RTMP protocol, right? Sounds
like it's not a good option :P

>I started working on a third option, which is to have a RTMP server
> >written in haXe/Neko. This server can already stream FLV files to a
> >Flash client using RTMP. Its goal is not to replace Red5 since it's not
> >supposed to be an application server but a media streaming server only.




That's great news! Good work, as always ;)

>No, if you want to know what is the "natural application server" for
> >haXe, I would say that's a haXe Remoting one. You can setup easily an
> >haXe HTTP Remoting server (which can't make calls but only answer your
> >requests)



What protocol does haXe HTTP remoting server use? Is it compatible with
AMF0/AMF3?

We are currently developing several projects using haXe Socket Remoting
> Servers, and when used together with haXe Remoting Proxy, it's very an
> incredible boost in terms of both productivity and quality of the
> resulting code.
>

That sounds very interesting and at the same time confusing. Could you point
me to resources (tuts/docs) about haXe Socket Remoting?

Thanks very much for your time,

Marcelo.

On 11/3/06, Nicolas Cannasse <ncannasse at motion-twin.com> wrote:
>
> > Hello,
> >
> > With the advent of Red5 (btw, congrats to the red5 team!), many people
> > are starting to discover the wonderful world of the rtmp protocol. The
> > ability to push data to the client is awesome. My networking knowledge
> > is somewhat limited, however. HaXe is a unique platform and such as, I
> > was wondering what would be the equivalent of Red5/FMS for haXe? Am I
> > able to use the RTMP on haXe flash apps? What about haXe socket
> > communication when the two sides (client/server) are both built on haXe
> > (flash/neko)? Which is the preferred communication method when it comes
> > to rtmp?
>
> When your client is Flash and your server is Red5, you can simply use
> Flash API to perform RTMP communications (It would be interesting to
> have a haXe Remoting API wrapper but you don't need it right now).
>
> Now if you want to replace your haXe/Flash client by a haXe/Neko one,
> you will have to manually connect using a neko.net.Socket and manage the
> RTMP protocol by-hand.
>
> I started working on a third option, which is to have a RTMP server
> written in haXe/Neko. This server can already stream FLV files to a
> Flash client using RTMP. Its goal is not to replace Red5 since it's not
> supposed to be an application server but a media streaming server only.
>
> No, if you want to know what is the "natural application server" for
> haXe, I would say that's a haXe Remoting one. You can setup easily an
> haXe HTTP Remoting server (which can't make calls but only answer your
> requests) or go for a haXe Socket Remoting Server, by using
> neko.net.ServerLoop and neko.net.RemotingBuffer classes. It's more
> difficult to setup but it works great.
>
> We are currently developing several projects using haXe Socket Remoting
> Servers, and when used together with haXe Remoting Proxy, it's very an
> incredible boost in terms of both productivity and quality of the
> resulting code.
>
> Nicolas
>
>
> --
> haXe - an open source web programming language
> http://haxe.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.motion-twin.com/pipermail/haxe/attachments/20061103/ca4b4e9a/attachment.htm