I got the same working. It seemed to be like a time out
issue from our
end. The network connections were taking too much time after
a point. I
was using non blocking api's .
We still face some problem. Attimes the login gets through
and attimes
not. We are attributing it to the slow network connections.
Thank you for the reply.
Regards
Prima
>-----Original Message-----
>From: loudmouth-bounces lists.imendio.com
>[mailto:loudmouth-bounces lists.imendio.com] On
Behalf Of ext
>Senko Rasic
>Sent: Sunday, December 09, 2007 9:14 PM
>To: Loudmouth List
>Subject: Re: [Loudmouth] Issue in SASL authenticate
after
>sending bindresponse.
>
>Hello,
>
>prima.dona nokia.com wrote:
>> After that I am not getting any response from the
server. I
>don't get
>> any callback to the socket_in_event() method in
LM.
>>
>> Nor do I get any call to the bind handler that is
registered.
>>
>> Is there something amiss?
>
>Are you using blocking or non-blocking API? Blocking API
>hasn't been thoroughly tested in 1.3. I'm just working
on
>fixing SASL + blocking API for 1.3.3, and I'm
experiencing
>similar problems, which are in my case caused infinite
blocking reads.
>
>Regards,
>Senko
>_______________________________________________
>Loudmouth mailing list
>Loudmouth lists.imendio.com
>h
ttp://lists.imendio.com/mailman/listinfo/loudmouth
>
_______________________________________________
Loudmouth mailing list
Loudmouth lists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth
|