On Wed, Mar 3, 2010 at 7:39 PM, Carlo Camerino <[email protected]> wrote: > will camel-mina support mina 2.0? > i think it has support for request reply >
Mina 2.0 is not GA yet. They are still working on it, although it appears to take a very very long time for them to get it done and released. > On Thu, Mar 4, 2010 at 2:36 AM, Claus Ibsen <[email protected]> wrote: >> There is no correlation with Mina 1.x. Its very low level and you >> gotta deal with that yourself. >> >> Its my hope that Mina 2.0 or Netty has some sort of build in support >> for correlation in its core. >> But you gotta look at that yourself, so read the Mina or Netty documentation. >> >> >> On Wed, Mar 3, 2010 at 7:31 PM, Carlo Camerino <[email protected]> >> wrote: >>> i used sync =true, i'm still got replies from another thread.... >>> >>> On Thu, Mar 4, 2010 at 2:20 AM, anandsk <[email protected]> wrote: >>>> >>>> when you use from it becomes the consumer and listens on that port if your >>>> app is running on host. >>>> >>>> If you are trying to identify the corresponding reply to a request, I >>>> beleive you need to have something in message to identify it uniquely. >>>> other >>>> alternative is using synchronus request/reply by setting sync flag to true. >>>> >>>> Thanks, >>>> Anand >>>> >>>> >>>> >>>> carlo c wrote: >>>>> >>>>> i was able to use codec successfully, >>>>> >>>>> however, i am having problems with the replies, >>>>> >>>>> sometimes i get the reply of another thread using the camel mina >>>>> component. >>>>> >>>>> how do i ensure that i am getting the proper reply >>>>> >>>>> i used the following >>>>> >>>>> mina:tcp://host:port?codec=#codecFactory >>>>> >>>>> how can i ensure that the reply is for me? >>>>> >>>>> what i did was to limit the number of consumers to 1 however i don't >>>>> wnt to do this in the future, >>>>> >>>>> the alternative that i could think is to set a separate >>>>> >>>>> from("mina:tcp://host:port?codec=#codecFactory") thread, is this the >>>>> correct way to handle this and set sync to false.... >>>>> >>>>> On Wed, Mar 3, 2010 at 5:04 AM, anandsk <[email protected]> wrote: >>>>>> >>>>>> If I understand your question correctly, you may want to look at codec >>>>>> option >>>>>> of camel-mina component. >>>>>> >>>>>> Thanks, >>>>>> Anand >>>>>> >>>>>> >>>>>> carlo c wrote: >>>>>>> >>>>>>> hi there, >>>>>>> >>>>>>> thanks a lot!! >>>>>>> i'm trying to understand the code in camel-mina and it seems that you >>>>>>> can configure it to signify that it is a textline? correct? >>>>>>> but what if the message returning isn't a text line. >>>>>>> In our case for example, the sample code that i use is >>>>>>> >>>>>>> dis.available() to determine if a message arrived, >>>>>>> afterwards, i configure a new byte[] in order to be able to read the >>>>>>> message >>>>>>> >>>>>>> Here is my source code using native java.io api >>>>>>> // input stream declaration coming from Socket >>>>>>> DataInputStream dis = **/ >>>>>>> // i'm checking this method (dis.available()) --> this returns the >>>>>>> number of bytes that an incoming message contains >>>>>>> byte[] responseByte = new byte[dis.available()]; >>>>>>> // >>>>>>> dis.readFully(responseByte); >>>>>>> >>>>>>> i somehow do it like this, >>>>>>> is there anyway that i can do this in camel mina? >>>>>>> i need to be able to get a response via the size of the input stream >>>>>>> coming back. >>>>>>> >>>>>>> thanks >>>>>>> carlo >>>>>>> >>>>>>> >>>>>> >>>>>> -- >>>>>> View this message in context: >>>>>> http://old.nabble.com/Question-On-Camel-Mina---Multiple-Messages-With-One-IOSession-tp27756509p27761139.html >>>>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/Question-On-Camel-Mina---Multiple-Messages-With-One-IOSession-tp27756509p27771764.html >>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>> >>>> >>> >> >> >> >> -- >> Claus Ibsen >> Apache Camel Committer >> >> Author of Camel in Action: http://www.manning.com/ibsen/ >> Open Source Integration: http://fusesource.com >> Blog: http://davsclaus.blogspot.com/ >> Twitter: http://twitter.com/davsclaus >> > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
