qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maki Camara <Maki.Cam...@etu.enseeiht.fr>
Subject RE: Non blocking receive qpid proton
Date Tue, 16 Apr 2013 17:38:21 GMT
Ok,

Thank you Jason


On Tue, 16 Apr 2013 18:34:28 +0100, Jason Barto wrote:
> Apologies, I typed before thinking. To address you're concern you'll 
> still
> have the while (true) you're trying to avoid but the cpu consumption 
> you're
> trying to avoid will be pushed onto the messaging library and should 
> be
> pretty easy on cpu.
>
> Sincerely,
> Jason
> On Apr 16, 2013 6:21 PM, "Jason Barto" <jason.p.barto@gmail.com> 
> wrote:
>
>> In the spawned thread, rather than while(true) couldn't you register 
>> a
>> handler function or functions with the spawned thread, from the 
>> thread call
>> recv (), which blocks, and then pass the received message to the 
>> registered
>> handlers?
>>
>> Sincerely,
>> Jason
>> On Apr 16, 2013 6:13 PM, "Maki Camara" <Maki.Camara@etu.enseeiht.fr>
>> wrote:
>>
>>> Connor,
>>>
>>> I have thought of delegating the recv to another thread, but what I 
>>> would
>>> like to have idealy is to
>>> avoid the loop(while(true)) to ensure minimal use of the cpu
>>>
>>> Thank you for your response,
>>>
>>> Maki
>>>
>>> On Tue, 16 Apr 2013 16:54:50 +0000, Connor Poske wrote:
>>>
>>>> Maki,
>>>>
>>>> An asynchronous event-listener interface would be a nice 
>>>> convenience,
>>>> but wouldn't simply blocking on recv() in another thread suite 
>>>> your
>>>> needs?
>>>>
>>>> Just spawn a thread from your main process to do receiving, while
>>>> main does whatever other work it needs to do.  This way your 
>>>> process
>>>> is not blocked.
>>>>
>>>>
>>>> ______________________________**__________
>>>> From: Maki Camara [Maki.Camara@etu.enseeiht.fr]
>>>> Sent: Tuesday, April 16, 2013 9:37 AM
>>>> To: users@qpid.apache.org
>>>> Cc: dpierce@redhat.com
>>>> Subject: Re: Non blocking receive qpid proton
>>>>
>>>> Yes that's exactly what I'm looking for. Is there any mean to do 
>>>> that?
>>>>
>>>> Thank you
>>>>
>>>> On Tue, 16 Apr 2013 11:27:20 -0400, Darryl L. Pierce wrote:
>>>>
>>>>> On Tue, Apr 16, 2013 at 04:54:15PM +0200, Maki Camara wrote:
>>>>>
>>>>>> THank you rafael,
>>>>>>
>>>>>> Sorry, I do not have a good english, I am using messenger, 
>>>>>> setting
>>>>>> the time out to zero can be useful...
>>>>>> I want my process be notified of the arrival of a new message in

>>>>>> the
>>>>>> incoming queue(like a events...)
>>>>>> As long as this event doesn't occur, I can do another thing.... 
>>>>>> and
>>>>>> when it occur, I will call messenger.recv(0)...
>>>>>>
>>>>>> Is this more clear
>>>>>>
>>>>>
>>>>> You want something more along the lines of registering a listener
>>>>> type
>>>>> that's called when a new message arrives, is that it?
>>>>>
>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: 
>>>> users-unsubscribe@qpid.apache.**org<users-unsubscribe@qpid.apache.org>
>>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>>
>>>>
>>>> ------------------------------**------------------------------**
>>>> ---------
>>>> To unsubscribe, e-mail: 
>>>> users-unsubscribe@qpid.apache.**org<users-unsubscribe@qpid.apache.org>
>>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>>
>>>
>>>
>>> 
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail: 
>>> users-unsubscribe@qpid.apache.**org<users-unsubscribe@qpid.apache.org>
>>> For additional commands, e-mail: users-help@qpid.apache.org
>>>
>>>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message