GTalk ping pong done.
Today we got the stanza ping pong for negotiating a GTalk voip connection working.
We found that the GTalk protocol might have changed, since the version used of Jabbin, which we test against.
We still have the JID issue. We can't get the full jid from the Jabber plugin. This leaves us with some different paths to solved the issue.
1) Make a core patch, so we can get it from the Jabber protocol.
2) We can gather information of the people in our friend list, so the information is ready when needed.
3) We can query the information (dunno how yet) and wait for the answer.
If we choose 2) we need to find an appropriate data structure to find for the buddy details.
We also have to look into Disco and stuff like that.
Cya friday
We took friday off. So status qo. I spend all night at work browsing the pidgin/jabber code/API trying to see if i could get the resources from there. It is for sure not possible to take it out from the Jabber plugin because we can not access the jabber_buddy functions which we like to. I still have a faint hope getting it out of the pidgin_notifty_user_info struct... but its a hack to get it out that way, since the object is used for UI.
So still status qo though my hair might be a bit grayer!
15/6 Our solution to this huge problem can be found in this post...
We found that the GTalk protocol might have changed, since the version used of Jabbin, which we test against.
We still have the JID issue. We can't get the full jid from the Jabber plugin. This leaves us with some different paths to solved the issue.
1) Make a core patch, so we can get it from the Jabber protocol.
2) We can gather information of the people in our friend list, so the information is ready when needed.
3) We can query the information (dunno how yet) and wait for the answer.
If we choose 2) we need to find an appropriate data structure to find for the buddy details.
We also have to look into Disco and stuff like that.
Cya friday
We took friday off. So status qo. I spend all night at work browsing the pidgin/jabber code/API trying to see if i could get the resources from there. It is for sure not possible to take it out from the Jabber plugin because we can not access the jabber_buddy functions which we like to. I still have a faint hope getting it out of the pidgin_notifty_user_info struct... but its a hack to get it out that way, since the object is used for UI.
So still status qo though my hair might be a bit grayer!
15/6 Our solution to this huge problem can be found in this post...
posted by hansson at 7:35 AM
0 Comments:
Post a Comment
<< Home