I'm not quite sure what your question is, so let me describe an experience I had. It might help you.
Many years ago I did some work on a local craft terminal for a piece of telecom equipment. This was back in the days when Sun was realizing just how bad the event model in Java 1.0.1/1.0.2 was. The company wanted many users to be able to connect to the piece of equipment at one time, but the socket-based interface provided on the machine would only accept one connection at a time. Last minute changes in requirements, etc. The way I handled this was to write a mediator to sit between the piece of telecom equipment and the many users. It worked by first connecting to the telecom equipment and then waiting for incoming connections to it. I published a port which would accept incoming connections (Java ServerSocket), vector those connections off to a temporary socket, and, incidentally, wrap those sockets with a thread waiting for incoming messages. Each time an incoming message was recognized I'd generate a UUID, and use the UUID as a message identifier for the message to the telecom equipment, as well as storing the UUID and the socket in a map. When the telecom equipment responded, I'd use the UUID to look up the socket, and write the response on the socket. (I'm skipping some details here, such as a timeouts, storing the original message id, replacing the UUID in the response with the oringial message id, PrintWriters, etc.) So, many users could interact with the mediator, and it took care of routing messages properly to and from the machine. Of course, you might just be looking for a "HelloWorld" for BlazeDS ( http://opensource.adobe.com/wiki/display/blazeds/BlazeDS). You tell me. If so, this: http://blog.everythingflex.com/2008/01/31/blazeds-vs-livecycleds/and this: http://www.dcooper.org/blog/client/index.cfm?mode=entry&entry=8E1439AD-4E22-1671-58710DD528E9C2E7might be of use. I hope this was of some use to you. Patrick -- On Thu, Oct 2, 2008 at 2:33 PM, Atlanta Geek <[EMAIL PROTECTED]> wrote: > Hi all, > I've been doing some development replacing a client/server app with a > Flex/Web/Server app. This is in cases where we need faster screen > updates than 1 or 2 a second that you can get with http. > This usually consist of rewriting a socket protocol written in C to a > flex app. An example of this is here: > http://www.atlantageek.com/?page_id=44 . This app slows down quite a > bit when multiple people are logged in. > > It has been really difficult to convert the blocking algorithms (wait > for a response) that I've seen in the C code to truly event driven > algorithms (Send a message, note message in a queue, event occurs with > response. Match response with queue item. Do next step in state > machine.) > Has anyone done much of this type of stuff. This seems like an obvious > place for flex. Is there example code or some sort of recipe to follow > so that I can verify I am doing things right. > > -- > Stability is for the weak!!! > Long live the next big thing. > > > ------------------------------------------------------------- > To unsubscribe from this list, simply email the list with unsubscribe in > the subject line > > For more info, see http://www.affug.com > Archive @ http://www.mail-archive.com/discussion%40affug.com/ > List hosted by http://www.fusionlink.com > ------------------------------------------------------------- > > > ------------------------------------------------------------- To unsubscribe from this list, simply email the list with unsubscribe in the subject line For more info, see http://www.affug.com Archive @ http://www.mail-archive.com/discussion%40affug.com/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
