The intent is to define a simple underlying protocol that we can all share, if you want all those extras Sky has, by all means use it. Different mod developers can share the same channels and not interfere, they can write their own libraries, and most importantly, they won't be making users fill up their chat channels with communication channels that are only used by one mod. The intent here is to provide a protocol everyone can use. People like to hold grudges and can be quite fickle you know. Some people flat out REFUSE to use Sky or any mods that use it, for whatever their reasons. Why not just take it and improve it to work the way you need? - AlexanderYoshi The main goal is to create a standard! So nobody has to rely on one specific addon. I had put that there when I was thinking "only one mod should perform the channel switch", but it's not a problem if many duplicate join channel calls are made. I see what you're talking about and yea, it's not needed. OMG inline replies! I'm too used to forums and not used to wikitalk, this is neat :) I'll tweak my replies to fit that "standard". And then again, if another addon already joined the new channel, fine, if not, join it. They just need to check if the user still is in the old channel, if yes then leave it and schedule a 'channel join' in 1 second. IMO addons don't need to know whether another addon is already preforming the channel switch or not. Tekkub 17:31, 9 July 2006 (EDT) I didn't mean the groupleader name in the channel, but the 'groupleader' variable in AddonCommRegistrar. It'll help people know they're in the correct channel, and they won't freak out at the "weird channel with all these numbers" they keep seeing. But the though twas that we wanted some semblance of user-readability in the channel name. No, frankly me and a few others (Satrina) would be totally fine with CommRa(Checksum). I'm doing JoinChannelByName() even if I'm already in the channel and I haven't seen anything bad happen, joining the same channel twice works fine.
After one second the second addon joins the new channel, after another second the first addon sees that the first channel is available and doesn't need to do anything. Is 'groupleader' in AddonCommRegistrar needed? let's say there are two comm addons, on leader change the first leaves the channel and schedules to join the new channel in 2seconds, the second addon immediately sees that the channel isn't available anymore (and maybe does something, like informing it's clients etc) and schedules a 'join' in 1 second.
0 kommentar(er)
