[Torseq Tech.]

What Tim said, ned, is correct. It's called YMSG/HTTP because it's actually YMSG protocol over HTTP protocol (YMSG packets encapsulated inside of HTTP). I probably should have specified by naming the actual option in Messenger to use. In this case if you open Messenger and then go to preferences, then Connection and choose the radio/option button called "Firewall with no proxies" apply then ok you'll sign into the network with YMSG/HTTP. It's also important to mention that you should go to Messenger's preferences and then to the "Ignore List" section and apply the "Ignore anyone who is not on my Messenger List" so if you are being PM bombed or other the packets will be ignored locally. The only thing that can bother you in this case would be add buddy requests but those won't be all over your screen if you're attacked but instead isolated (overlapping one another) since the "Ignore anyone who is not on my Messenger List" option doesn't stop you from seeing those.

After you do this do not enter chat just leave it in "pager mode" signed into Messenger. After this is done the same ID you used to sign into YMSG/HTTP with use that ID to sign into Chat 2 protocol on either the browser DHTML chat (which uses Chat 2) or a separate 3rd party client. You could leave the YMSG/HTTP messenger session minimized but still active and just focus on your Chat 2 session inside the 3rd party client or DHTML browser page (whichever means you go about when using Chat 2).

This works because YMSG protocol (including YMSG/HTTP) has priority/precedence over Chat 2 protocol and it overrides all of the packet types that you can receive such as chat invites and PMs. There's a way to toggle this back and forth from the YMSG connection not getting priority and the chat 2 connection receiving the PMs and chat invites but then this will make your chat 2 connection "bootable" by means of flooding (back to square one). What could be done is to toggle it on when you're not under attack *so you can receive your PMs and chat invites on the Chat 2 connection normally* and when you are under attack shift the priority back to YMSG/HTTP receiving that traffic so your Chat 2 (room) connection is unaffected. Let me know if you're wanting to know how to change that up and I can share that information.