Most features in mIRC are designed to be network resource-friendly. In this particular case, since the large majority of users don't need the IAL to be filled, making mIRC do this automatically would be a waste of IRC network resources. Many users join channels and idle for extended periods of time, and such an automated feature would end up being the reason for much of their network resource usage. This is why the scripting language supports the IAL, to allow those who need it to use it.
Khaled, /userhost, as you know, returns one line back for each one sent. So, the only way it would be resource intensive is if the client didn't throttle it's output. mIRC uses /userhost for commands such as /ban and /dns when that user is not in the IAL. Perhaps you should explain why you choose /userhost vs. /who. I don't think anyone else here has any idea what the intent of the /userhost command is. It probably is the most network-resource friendly command used by IRC servers. Honestly it's about as resource intensive as using the /ison command for checking the notify list on legacy servers.
Listen Khaled, if you know a more effecient way of obtaining the information for a complete IAL, I would like to here it. Honestly, why have an IAL if mIRC can't fill it on it's own? People can script there own IAL's too.
Listen, this feature could be enabled or disabled the same way you could originally enable or disable the IAL. Leave it disabled by default. You would might be surprised how many people actually enable it and *like* this feature.
