advertisement

Weblog:   Blame the last man standing?
Subject:   Rendezvous ill accused probably.
Date:   2003-07-15 00:19:35
From:   joccam
First of all, there were many powerbooks and ibooks at OSCon. It was great to see. I heard anecdotally this was the first year with such a trend. I'd guess upwards of half the portables were powerbook (plus a few ibooks). Amazing. So, there were plenty to go around.


However at Apple's WWDC the week before, there were probably twice as many people who virtually all had powerbooks or ibooks. There were network problems initially, but by the end everything was working well (when you could get an IP address from DHCP). IOW, no rendezvous issues in a much heavier wireless network situation.


Based on this (unscientfic) perspective, I'd guess Rendezvous had little if anything to do with the network outages. I noted that to my session neighbors during the break when the announcement was made, and saw nothing which cast Rendezvous in doubt.


Eventually they got the network working, and it wasn't immediately after the announcement (when everyone would have killed Rendezvous).


2c,


= Joe =
Full Threads Oldest First

Showing messages 1 through 1 of 1.

  • Rendezvous ill accused probably.
    2003-07-15 17:35:59  anonymous2 [Reply | View]

    "There were network problems initially, but by the end everything was working well (when you could get an IP address from DHCP). IOW, no rendezvous issues in a much heavier wireless network situation."

    I was also at WWDC. One time I enabled Rendezvous in iChat, and the next thing I knew, the "mDNSResponder" Multicast DNS responder process was eating my PowerBook G4 17" CPU alive. 75% or thereabouts of the CPU was being eaten by this thing. I hate to say it, Stuart, but even if Rendezvous wasn't the cause of the problem with the network(s), it sure was a problem on my CPU. I immediately turned it off in iChat and things returned to normal.
Showing messages 1 through 1 of 1.