Comments on: AIR 2 Chat Server & Client https://jessewarden.com/2009/12/air-2-chat-server-client.html Software | Fitness | Gaming Thu, 04 Jul 2013 14:40:45 +0000 hourly 1 By: Brian Lesser https://jessewarden.com/2009/12/air-2-chat-server-client.html/comment-page-1#comment-212033 Sun, 13 Dec 2009 04:18:06 +0000 http://jessewarden.com/?p=1860#comment-212033 Adobe added application-level code to insure data messages are sent without loss in RTMFP.

Writing P2P applications is very different from writing socket server applications. Both are useful.

]]> By: Joeflash https://jessewarden.com/2009/12/air-2-chat-server-client.html/comment-page-1#comment-211292 Tue, 08 Dec 2009 19:21:41 +0000 http://jessewarden.com/?p=1860#comment-211292 Ah, yes that makes sense: chat is unreliable with RTMFP because UDP is a lossy transmission protocol — great for streaming media, crap for messaging, at least without some kind of feedback error-correction (did the message get there?), which would be extra work.

]]> By: JesterXL https://jessewarden.com/2009/12/air-2-chat-server-client.html/comment-page-1#comment-211290 Tue, 08 Dec 2009 19:01:13 +0000 http://jessewarden.com/?p=1860#comment-211290 2nd paragraph describes it well:

http://en.wikipedia.org/wiki/User_Datagram_Protocol

]]> By: Joeflash https://jessewarden.com/2009/12/air-2-chat-server-client.html/comment-page-1#comment-211289 Tue, 08 Dec 2009 18:58:03 +0000 http://jessewarden.com/?p=1860#comment-211289 Good point. Why is there no guaranteee — because of most firewall settings?

]]> By: JesterXL https://jessewarden.com/2009/12/air-2-chat-server-client.html/comment-page-1#comment-211239 Tue, 08 Dec 2009 00:46:00 +0000 http://jessewarden.com/?p=1860#comment-211239 The important difference is RTMFP is UDP, whereas Socket/ServerSocket is TCP/IP. If I send a chat message via UDP, there is no guarantee it’ll get there, whereas with Socket, there is. TCP, however, isn’t as good for sending video & audio because you want speed.

]]>