At first I was a little skeptical of this comment–I even Googled the username to see if the user was associated rhubcom.com (which she doesn’t appear to be).

Meh, I think that while Web conferencing should be bullet proof–things aren’t a whole lot different from 10 years ago. It’s which one sucks less for what you want to do.

And, that doesn’t explain why when I said deny WebEx didn’t provide any guidance/help explaining why that unrestricted access is necessary. Nor did WebEx provide any information ahead of time what to expect. I don’t recall if I checked the details tab for information or not, but I’m guessing I did try it, and I don’t recall getting any usable information there either. All of that’s should be in WebEx’s control, no?

For what it’s worth, I was in a four site conference with a major publisher. After having getting dumped out a couple times, I signed in with a username of “WebEx Sucks”. By the time we were done, and after having the host get dumped out, he agreed with the sentiments expressed by my username.

I am the Product Manager for WebEx, responsible for cross platform support. The Java applet message is not WebEx message; this is a standard message that comes from the operating system (Mac OS 10.5 in this case). If we were to prevent this message, it could introduce security risks. I do think that Apple should update the text of this dialog though.

The out of memory error message should not have been displayed as the problem has nothing to do with memory. This has been resolved in the latest WebEx version (WBS 27). You were using version WBS 26 which is what intercall.webex.com is running.

Thanks.
–Sanjay