Let me prefix this slightly by saying I’‘m having a little trouble following what you are asking. I’'m going to try to answer but I may have missed your point.
One more thing !
I want the user of my client to select to which transports it wants to login on startup
let’'s say client has registered his/her hotmail, yahoo accounts for his jabber id now i do following steps
- Ask user to check the transports to which it wants to signin in a screen.
- If user selected hotmail only i would not like to send instead i should send to login hotmail account only .
- if user selected both i will send 2 presence messages
Now these are the cases where i cant send message , tell me is there anyother way to do that.
Since using i cant get presence messages of my hotmail contacts from server.
Note: After login using i get jabber:iq:roster query
iq type=set to=tcm@ MyWildfire /mobile id=480-17 ==
query xmlns=jabber:iq:roster ==
item name=Change your picture jid=mawaisanwar%hotmail.com@msn. MyWildfire subscription=both ==
group == MSN Contacts
Is this only after the first time you log in? The plugin looks at your roster and fixes your subscripting for you. You shouldn’'t get that multiple times.
Should I send back something to server so that I can get those presence messages now? If yes what should be that message.
Will really appreciate a quick response since I am stuck with this problem since last many days.
If you didn’‘t send a global presence to the wildfire server itself, you shouldn’'t be able to do much at all really. You need to tell the wildfire server itself that you are loged in. =/
That said, I was looking over XEP-0100, section 4.1, a tad, and I believe I’‘ve screwed something up. Specifically, step 7 is supposed to be optional for the -client-. The thing is, when someone registers with me, I am forcibly putting the JID of the transport in their roster. This is “not cool”. By doing that I’‘m screwing over your ability to choose to not have it in your roster, and therefore the transports wouldn’‘t automatically get presence. By -not- having the transports in your roster, you would easily be able to set it up so that the user can choose whether they want to automatically log into the transport services or not. We set up something weird like this for Spark but it looks like I was doing something dumb to begin with and should have let the client “do their job”, ya know? If I’'m reading you right, fixing this issue would allow you to get around the problems you are running into.