Any way to display Presence text?

Michael B.

Could you please be more specific.
Please let us know more details about the problem.

Thanks.

Keep in mind that AIMCC is apartment threaded. It's natural for Java developers to want to call AIMCC from multiple threads, but that's not supported. Each AccSession must be instantiated and called from a single thread.

I am newly assigned to the task of developing a BOT application in Java. There is something that I still don't understand.

Keep in mind that AIMCC is apartment threaded. It's natural for Java developers to want to call AIMCC from multiple threads, but that's not supported. Each AccSession must be instantiated and called from a single thread.

I am trying to reconcile the above statement with the approach recommended in the Creating AIM-Enabled Applications in Java, Part 2 article.

The statement implies the need for multiple threads, each with its own AccSession. The article, on the other hand, uses a single thread which segregates each user's data from other users by introducing a "Conversation" data container object, but these objects do not live in separate threads. They are all on the same thread.

My question is this: To implement the multi-threaded model, the original contact between a new user and a bot comes in as an IM to a "Dispatcher" object which keeps track of the the threads it has spawned. SOMETHING has to spawn these threads. This dispatcher must itself create an AccSession to learn the basic info about the user. If it determines that this user is new, it willlaunch another thread which would create another AccSession to handle that user.

My question is this:

By what mechanism does the AccSession that received the initial IM for a user "pass control" of the conversation to a new
AccSession?

Multiple threads aren't needed; they're an option. All of the calls and events associated with each IAccSession are in the thread in which the IAccSession was created. Each IAccSession does its own communication with the servers; the IAccSessions know nothing of one another.

That is interesting to know (would be good to have in the Javadocs, if it is not there already).

I'm wondering -- would creating some sort of synchronization wrapper around AIMCC calls solve this problem?

Perhaps something could be added to the API in the same vein as java.util.Collections.synchronizedCollection?

Thanks for the feedback. I'm passing the suggestion along.

Yes, it seems to be a case here.
I have found that one of the actions we had in our code did not do that from the same thread that owns AccSession.
Since we changed that we did not face the problem anymore.