Quote Originally Posted by 'BobGnarly',index.php?page=Thread&postID=165653#po st165653
Premise: UnitExists() returns nil if you are logged out or if the character really doesn't exist.

If this is true, why not just use it to query the "existence" of the team member before you ever send them a message? I know this might not alert you to the case where you typo'd the name, but I think you'd notice that pretty quick when it wasn't working with one of your clients. The result would be quite a bit more elegant I think, it could probably be handled with something like:
Thanks for your post. UnitExists is only valid if the unit you are querying is in your party or raid. I could have two of my characters next to each other (not grouped) and they would not know about each other. I frequently hit the Taxi, before I've gotten around to inviting my my characters to a group. Plus, the 6+ boxers might like to Taxi characters around using Jamba, and the UnitExists() would not work for them.

Oh, how I wish for stateless... I'm happy with my current solution (one more bug to fix) which is the channel join/leave/list members approach (no messages are ever sent on the channel). Basically I let WoW do my record keeping for me. My other characters status changes on my screen when they come online / go offline within a few seconds. It is very sweet compared with the enabled/disabled confused mess the current Jamba has.