Well, you could also look into an existing Socket server to handle your messaging teer. I'm working on an applicatino that utilizes XMPP for the "push" mess ageing layer. There is even a really good AS2 library for utilizing the XMPP protocol. You can find this stuff here: http://jivesoftware.org It's open source and free.
There are others that don't use XMPP out there specifically geard towards Flash as well, like Oregano: http://www.oregano-server.org/ and ElectroServer: http://www.electrotank.com/electroserver/ In addition, as Grant already mentioned, you can use RTMP with FCS, or Red5. There are several advantages with using RTMP as opposed to the XMLSocket connection. Binary format as opposed to Strings, can pass actual Data types to the server, can stream audio and video are just a few. Red5 will also be able to utilize AMF messaging and will be able to integrate with server-side infrastructure through the Spring Framework. A 1.0 release of Red5 is scheduled for Spring of 2006, so if you have time to wait, it might be worth looking at. You can see more on the project here: http://osflash.org/red5. And if you have the cash then definitely use FCS. I hope that helps give you some other options to choose from. -Chris On 11/4/05, Tracy Spratt <[EMAIL PROTECTED]> wrote: > Thanks, all, good advice. > Since my requirements as very specific and I have control over all > levels, and I have a bit of experience with .net socket programming, I > plan to implement this as a .net socket server talking to XMLSocket AS > clients. > > Jeremy and Jim, you both implied I could "..use a single port and send > to a specific destination." I'll take this question over to a .net > forum, but my limited understanding of socket programming does not > include how this could work. Any follow up hints will be appreciated. > > Worst case, client filtering does not scare me. > > Thanks again, > Tracy > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Larkin, > Jeremy > Sent: Friday, November 04, 2005 3:18 PM > To: Flashcoders mailing list > Subject: RE: [Flashcoders] Need advice on XMLSocket architecture > > Keep in mind that you can use a single port and send to a specific > destination. If you can identify the client specifically, then this > should be pretty easy. That would allow you to send messages only to the > clients that require the message. Creating a separate port for each > connection would not scale well (I know you said this wasn't so much of > an issue) and it could potentially be an administration nightmare. > > With that said, there are a number of free servers out there. Oregano > (java-based) comes to mind. You had mentioned .NET, are you looking > specifically for a .NET server? I don't know of any offhand, but I > vaguely remember coming across one, maybe search on source forge. If you > are familiar with network programming, it is possible you could roll > your own if it has a specific need. What I mean is that it is not too > difficult to build something if a) you know how to build it (duh), and > b) the solution is very specific. The difficulty of writing a server > comes with all the options (plugins, clustering, highly customizable > messaging data, etc.). > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tracy > Spratt > Sent: Friday, November 04, 2005 2:44 PM > To: [email protected] > Subject: [Flashcoders] Need advice on XMLSocket architecture > > Hello, I'm a regular on the flexcoders list, where it was suggested > that I ask my question over here. Any advice will be welcome! > > I have 100 fixed, identifiable clients running a Flex 1.5 app on an > intranet. A Dot.Net integration tier maintains individual states for > each client. The integration tier talks asynchronously to third party > apps over async tcp sockets and even mail transport. I had planned on a > leisurely polling setup to get the clients updated with changes in > state, but I now have a requirement for an update with minimum latency. > > The messaging between clients and server is very low frequency (a few > clients updated per minute) and very low message size (a few k per > update). > > I am now looking at a true "push" connection using XMLSockets. I see > two approaches: > > On would be to have a separate port connection for each client with each > client only getting their messages, the other would be a single port, > where all clients would get all messages, and ignore those that were not > theirs. > > In my case performance, reliability and simplicity are most important, > and scalability not so much an issue. > > Any suggestions, experiences, resources would be appreciated!! > > Tracy > > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > > > _______________________________________________ > Flashcoders mailing list > [email protected] > http://chattyfig.figleaf.com/mailman/listinfo/flashcoders > _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
