Skip to main content

To provide some background on this question, google talk uses xmmpxmpp (aka Jabber) which is an open Instant Messaging standard. As a part of this standard, every instant messaging client (chat in gmail and the android talk app) is assigned a Resource. The server then uses the resource to know which client is communicating.

This is how the interaction works: Say your gmail account is [email protected]. Then gmail chat might be [email protected]/gchat and the talk app [email protected]/talk

When your friend sueSue ([email protected]) wants to send you a message, she simply sends it to [email protected]. At this point, the server either sends the message to whichever client you used last, or sends the message to all currently connected clients (google does the latter).

When you reply to sueSue using the talk app, she receives the message from [email protected]/talk. Now, instead of sending further messages to [email protected], sue'sSue's client now sends messages directly to [email protected]/talk and will continue doing so until a message is received from some other client.

This means that what Saiboogu said should work. That is, to switch between clients, send a message to the person you are chatting with from the desired client.


**tl;dr: This happens by design, Saiboogu's workaround works.

To provide some background on this question, google talk uses xmmp (aka Jabber) which is an open Instant Messaging standard. As a part of this standard, every instant messaging client (chat in gmail and the android talk app) is assigned a Resource. The server then uses the resource to know which client is communicating.

This is how the interaction works: Say your gmail account is [email protected]. Then gmail chat might be [email protected]/gchat and the talk app [email protected]/talk

When your friend sue ([email protected]) wants to send you a message, she simply sends it to [email protected]. At this point, the server either sends the message to whichever client you used last, or sends the message to all currently connected clients (google does the latter).

When you reply to sue using the talk app, she receives the message from [email protected]/talk. Now, instead of sending further messages to [email protected], sue's client now sends messages directly to [email protected]/talk and will continue doing so until a message is received from some other client.

This means that what Saiboogu said should work. That is, to switch between clients, send a message to the person you are chatting with from the desired client.


**tl;dr: This happens by design, Saiboogu's workaround works.

To provide some background on this question, google talk uses xmpp (aka Jabber) which is an open Instant Messaging standard. As a part of this standard, every instant messaging client (chat in gmail and the android talk app) is assigned a Resource. The server then uses the resource to know which client is communicating.

This is how the interaction works: Say your gmail account is [email protected]. Then gmail chat might be [email protected]/gchat and the talk app [email protected]/talk

When your friend Sue ([email protected]) wants to send you a message, she simply sends it to [email protected]. At this point, the server either sends the message to whichever client you used last, or sends the message to all currently connected clients (google does the latter).

When you reply to Sue using the talk app, she receives the message from [email protected]/talk. Now, instead of sending further messages to [email protected], Sue's client now sends messages directly to [email protected]/talk and will continue doing so until a message is received from some other client.

This means that what Saiboogu said should work. That is, to switch between clients, send a message to the person you are chatting with from the desired client.


tl;dr: This happens by design, Saiboogu's workaround works.

Source Link
dave
  • 396
  • 1
  • 2

To provide some background on this question, google talk uses xmmp (aka Jabber) which is an open Instant Messaging standard. As a part of this standard, every instant messaging client (chat in gmail and the android talk app) is assigned a Resource. The server then uses the resource to know which client is communicating.

This is how the interaction works: Say your gmail account is [email protected]. Then gmail chat might be [email protected]/gchat and the talk app [email protected]/talk

When your friend sue ([email protected]) wants to send you a message, she simply sends it to [email protected]. At this point, the server either sends the message to whichever client you used last, or sends the message to all currently connected clients (google does the latter).

When you reply to sue using the talk app, she receives the message from [email protected]/talk. Now, instead of sending further messages to [email protected], sue's client now sends messages directly to [email protected]/talk and will continue doing so until a message is received from some other client.

This means that what Saiboogu said should work. That is, to switch between clients, send a message to the person you are chatting with from the desired client.


**tl;dr: This happens by design, Saiboogu's workaround works.