tag:blogger.com,1999:blog-8840085855436806841.post598573565105558364..comments2011-01-31T19:19:26.596-05:00Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-8840085855436806841.post-83639142455365645622011-01-31T19:19:26.596-05:002011-01-31T19:19:26.596-05:00I am interested as well :)Shannarahttp://www.blogger.com/profile/05700293580839115132noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-19486806943162710102010-01-27T04:45:35.240-05:002010-01-27T04:45:35.240-05:00Ryan, can you show a block of code that make the message exchange between flex and java using this approach?Thiagohttp://www.blogger.com/profile/06226665859485293563noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-33734515316182958772010-01-22T15:37:06.800-05:002010-01-22T15:37:06.800-05:00Hi Thiago, <br /><br />That&#39;s the exact approach I took and it worked very well for me. Best of luck on your game!Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-54008149793616766522010-01-22T08:24:44.802-05:002010-01-22T08:24:44.802-05:00Great post ryan. Can u give more details about the design of ProtocolCommand class and how you store the information?. Im developing a multplayer game flex/java using apache mina, and i define a class that have a header with OPCode, Lenght of body, and the Body (that is a ByteBuffer ), so in handler i identify the operation and extract the body information. Are you using the same aproach?Thiagohttp://www.blogger.com/profile/06226665859485293563noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-18701525539237524512008-10-20T07:48:00.000-04:002008-10-20T07:48:00.000-04:00Hey Ryan<BR/><BR/>thanx for a nice tip and some good piece of information<BR/><BR/>very useful blog - thanx again!<BR/><BR/>RegardsFlex programminghttp://www.iksanika.com/services/internet_intranet/flash_flex_multimedia.htmlnoreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-27235698457904530472008-10-09T14:13:00.000-04:002008-10-09T14:13:00.000-04:00Honestly, Donald, I'm not sure. I haven't reached it. The mina list/forums will probably know better.Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-62653684373412713592008-10-09T13:20:00.000-04:002008-10-09T13:20:00.000-04:00Hi Ryan,<BR/><BR/>Thank you so much for sharing!<BR/><BR/>I have a question:<BR/>I saw statements like "over 4000 concurrent connections ...". What does it really mean? What is the actual limitation on the max concurrent connections? <BR/><BR/>Thanks in advance<BR/><BR/>Donald拇指http://www.blogger.com/profile/10128910628731648931noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-50385694338474818532008-09-14T20:24:00.000-04:002008-09-14T20:24:00.000-04:00Hey narup, <BR/><BR/>I like to have a method in my Flex object representation of the protocol command called encode, such as encode():ByteArray, and a static method in the protocol command class called decode that will return an object representation of the particular command, such as decode(bytes:ByteArray):ProtocolCommand. In a language that supports overloading methods, like Java, I'd just overload the constructor to create one that accepts a Java ByteBuffer, but you can't do that in actionscript, so the static method works fine for decode. <BR/><BR/>So, when sending a command to the server, my client calls encode on the ProtocolCommand object I've created, which will return the appropriate ByteArray to write to the socket; and when receiving a command, my client calls the static decode method (using the ByteArray read from the socket as an argument), which will return a nice OO command representation. <BR/><BR/>So, yes, to a certain extent you have to interpret the bytes somewhere but, if done correctly, you'll only have to do it twice: once for outgoing, and once for incoming. I've seen some object representation standards which would let you skip ever dealing with the command as a byte[] and let you read/write objects, but I've never investigated them further, so I'm not sure on those.<BR/><BR/>Does that answer your questions?Ryanhttp://www.blogger.com/profile/12120844691062261364noreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-67148096109883430892008-09-14T19:04:00.000-04:002008-09-14T19:04:00.000-04:00hi Ryan, one question again :)<BR/>about the enocder/decoder in client side how are you reading the object from the socket, i can get the string as byte arrays, what if i want the complete oject, or i have to construct it myself on the client side based on received bytes. <BR/>thanksnaruphttp://narup.blogspot.comnoreply@blogger.comtag:blogger.com,1999:blog-8840085855436806841.post-51607493569383014232008-09-07T19:12:00.000-04:002008-09-07T19:12:00.000-04:00hey Ryan, <BR/><BR/>thanks for the post. it did help.naruphttp://narup.blogspot.comnoreply@blogger.com