Thank you for fixing double call of onDisconnect().
I mentioned two issues with not consistent calling of onDisconnect below.
Can you put you comments on it ?
1) Both pseudo code below have the same problem.
If server is down, then *only on first call of pClient -> connect();*
*OnDisconnect is not called.*
During next attempts of connect(), OnDisconnect is called.
for(int ic = 0; ic< 3; ic++ )
{
pClient = new Client();
pClient -> connect();
delete pClient;
}
pClient = new Client();
for(int ic = 0; ic< 3; ic++ )
{
pClient -> connect();
}
delete pClient;
2) connect() returns false when server is down, but there is not actual
error reason returned like in OnDisconnect().
Is it possible to fix this by always calling OnDisconnect() when connection
could not be established?
(or to make consistant bahaviour at least or to return errorid in
connect()?)
Thanks,
Anatoly
2007/3/6, Jakob Schroeter <js@xxxxxxxxxx>:
I released a new maintenance version.
Besides fixing the double call of onDisconnect(), I added a way to cancel
outstanding IQ and VCard operations.
<http://camaya.net/glooxchangelog>
Updated API docs:
<http://camaya.net/api/gloox/index.html>
cheers,
Jakob
--
gloox-dev mailing list
to unsubscribe:
send a message with subject 'unsubscribe gloox-dev' to
minimalist@xxxxxxxxxx