I made several assumptions on the types of contexts that could be selected on
and which ones to check the fd of after select. Maybe these assumptions are
flawed.
What exactly happens to the context when an async message is sent?
Check out modules/xmpp/xmpp_queue.c arolines
Got it.
Yep, its broken, definately, Now I have that description its obvious.
To fix the problem with re-used fd-s before contexts got cleaned / removed
and crashing and all that I went to great pains to ensure we only chose
contexts with activity on the fd to bind to. I didn't consider that
IG, I'm trying to test this but my pidgin won't connect.
It reports unknown error.
In the citserver log I get Ignoring unknown tag bind just before the
connection gets closed.
Wed Feb 24 2010 08:33:14 EST from IGnatius T Foobar @ Uncensored
Subject: Re: asynch not working
If you send a message from Cit client to pidgin the message doesn't arrive.
Got that bit.
Question. Does the message from Cit client arrive when pidgin sends a new
message to Cit client?
Wed Feb 24 2010 08:33:14 EST from IGnatius T Foobar @ Uncensored
Subject: Re: asynch not
If you send a message from Cit client to pidgin the message doesn't arrive.
Got that bit.
Question. Does the message from Cit client arrive when pidgin sends a new
message to Cit client?
It should, at least it did when I tested it.
Pidgin should also receive
