thanks alex ... On Sat, Jun 14, 2008 at 4:01 AM, Alex Karasulu <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 13, 2008 at 8:55 PM, islam el-naggar <[EMAIL PROTECTED]> > wrote: > > > hello thanks alex for ur reponse , i don't matter about request order > > but, i need to know what about it , what happened when i need to care > > about the order of the messages? > > > > Request order is easy enough but when your responses have to come back > respectively, then you need to synchronize your responses and that's a bit > of a headache. > > Alex > > > > > > thanks > > islam > > > > On Sat, Jun 14, 2008 at 3:42 AM, Alex Karasulu <[EMAIL PROTECTED]> > > wrote: > > > > > On Fri, Jun 13, 2008 at 8:14 PM, islam alnaggar < > [EMAIL PROTECTED] > > > > > > wrote: > > > > > > > thanks alex for ur reply > > > > my case that i have chat server must be able to serve multi > concurrent > > > > requests from many clients > > > > such as sending text messages then routing those messages to other > > > clients > > > > and i tested it and it works.. > > > > the issue is that same client have many requests simultaneous like > > > sending > > > > text messages, voip message , getting other voip messages, listen to > > > > changes in the user list , those all are concurrent requests per one > > > > client > > > > so i need to know the issue of the server side > > > > does it serve each request as is or packets override each others i > > dunno > > > > > > > > > > You can have many outstanding requests in transit or being processed by > > the > > > server from a single client but those requests will have to be laid out > > on > > > the wire serially. Your multi-threaded server will start processing > > those > > > requests and respond to the client (again don't know if order of > > responses > > > matter for you) most likely in separate threads. When these threads > > write > > > back to the session it will serialize those responses so the response > > PDUs > > > do not interleave. > > > > > > If response order does not matter to you, then it makes no difference > to > > > the > > > server whether responses to requests are to a single client or to > > multiple > > > clients. From the MINA standpoint they're simple requests that need to > > be > > > processed with responses written to some IoSession. MINA handles the > > rest. > > > > > > If response order does matter that's another story. > > > > > > Alex > > > > > > > > > > > > > > > > > thanks > > > > islam > > > > > > > > On Fri, Jun 13, 2008 at 8:39 PM, Alex Karasulu <[EMAIL PROTECTED] > > > > > > wrote: > > > > > > > > > On Fri, Jun 13, 2008 at 8:20 AM, islam alnaggar < > > > [EMAIL PROTECTED] > > > > > > > > > > wrote: > > > > > > > > > > > hello , > > > > > > i have client/server application i had wrote using mina framework > > > > > > so i have client do many requests simultaneous to server side > > > > > > like sending voip packets , getting text messages etc.. > > > > > > is there any problem with the threading issue, and i need to know > > the > > > > > > threading architecture that mina work with the same client .. > > > > > > > > > > > > > > > > The threading aspects of your protocol server depend on how you > > design > > > it > > > > > and the semantics of these simultaneous requests: i.e. do the > > requests > > > > from > > > > > the same client need to be handled in order etc. But independent > of > > > this > > > > > you of course want your server to be able to respond to multiple > > > > concurrent > > > > > requests at a time. You should not have any problem doing this > with > > > > MINA. > > > > > > > > > > Alex > > > > > > > > > > > > > > >
