Can only receive chats by polling about asmack HOT 10 CLOSED

Incidentally, I just figured out how to connect to google accounts:

Use XMPPConnection("gmail.com") and login("[email protected]", "password")

Could you add XMPPConnection.DEBUG=true; and Connection.DEBUG=true; before 
stating
the Thread? Can you provide a log of the messages send (minus the sasl part, of 
course).

What does "you can receive messages" mean? Can you receive messages in your 
loop and
in your chat manager or just in your loop?

TIA, René

I think I know this bug. You also need to listen for new Chats not only for 
Messages
in your existing chat since the ChatManager class in the original Smack has a 
bug
which creates for every incoming message a new Chat. This happens if the 
incoming
Message hasn't got a threadid or another threadid than the message you sent. 
Your
PacketCollector instead listens for all Messages it gets from the other JID no 
matter
what threadid they have. A PacketListener on the connection which listens for 
Message
packets should also work.

THX till, http://www.igniterealtime.org/issues/browse/SMACK-269 is what you 
mean,
right? Sounds like I should cherry-pick that one, too.

Any objectives?

Yeah, thats what I meant. At the moment I completely circumvent the ChatManager 
and
map the chats according to the jid. I'm completey ignoring the threadid since 
most
client don't set the threadid. This works pretty fine for me.

Ok, I'll have to read the spec, depending on that I'd
- clone the chat manager and provide a xmpp-thread-unsafe chat manager (if 
smack is
right)
- apply the patch (if smack is wrong)

http://xmpp.org/rfcs/rfc3921.html#rfc.section.2.1.2 looks like you're right. 
Clients
MAY send a thread-id for messages, but they aren't enforced to do so.

2.1.2.3 is even worse. Looks like messages should be grouped by 
jid,resource,thread
(with NULL being a correct value for grouping). Starting a thread with a thread 
id is
bad because we can't be sure if a reply (if any) will contain the thread id.

Google code and any RFC viewer should implement dislike button....

I see there's a new build of the code.  Has this issue been addressed in that 
build?  
Thx!

Just confirmed it's fixed with asmack-2010.04.02.jar.  Thanks!

Oh nice, didn't see the patch that fixed it, but glad to see your problem has 
been
addressed! Thanks for rechecking, and happy hacking!