Re: Xcode 3.0 delay

  • On Nov 1, 2007, at 10:55 AM, Chris Espinosa wrote:

    > and Xcode doesnt cuntinue until the DNS server times out.

    Wouldn't the obvious solution be to not have Xcode wait on a server
    timeout?

    Raffael Cavallaro, Ph.D.
    <raffaelcavallaro...>
  • It's not XCode - it's a network thing.
    We have an intermittent network issue here, where everything is happy
    for weeks, and then once in a while, XCode takes a minute to come up.
    We had tracked it down to a particular DHCP server (which we removed),
    in combination with Parallels installed on the machine. Other
    "network" aware clients exhibited the same problem.
    We think it's more of a Bonjour thing - XCode uses this for
    distributed compiles.
    In the case of XCode, static IP addresses resolved the issue.

    On Nov 1, 2007, at 11:23 AM, Raffael Cavallaro wrote:

    >
    > On Nov 1, 2007, at 10:55 AM, Chris Espinosa wrote:
    >
    >> and Xcode doesnt cuntinue until the DNS server times out.
    >
    > Wouldn't the obvious solution be to not have Xcode wait on a server
    > timeout?
    >
    >
    >
    >
    > Raffael Cavallaro, Ph.D.
    > <raffaelcavallaro...>
  • On Nov 1, 2007, at 12:08 PM, Tony Becker wrote:

    > Other "network" aware clients exhibited the same problem.

    My point is that this seems to be a bug in the "network aware" code in
    these clients - i.e., they wait on network responses rather than
    spawning a thread for the network request and not assuming in any
    downstream code that that request has actually returned.

    It shouldn't be possible for a network timeout to cause a properly
    written app to spin - the app should go on it's merry way with other
    tasks and then deal gracefully when notified of the timeout at some
    later point.

    Raffael Cavallaro, Ph.D.
    <raffaelcavallaro...>
  • FWIW, this sounds like a problem I have when using EyeTV.  When I
    start the program when there is some network problem, EyeTV takes a
    while before the beach ball stops spinning.

    On Nov 1, 2007, at 11:53 AM, Raffael Cavallaro wrote:

    >
    > On Nov 1, 2007, at 12:08 PM, Tony Becker wrote:
    >
    >> Other "network" aware clients exhibited the same problem.
    >
    > My point is that this seems to be a bug in the "network aware" code
    > in these clients - i.e., they wait on network responses rather than
    > spawning a thread for the network request and not assuming in any
    > downstream code that that request has actually returned.
    >
    > It shouldn't be possible for a network timeout to cause a properly
    > written app to spin - the app should go on it's merry way with other
    > tasks and then deal gracefully when notified of the timeout at some
    > later point.
    >
    >
    > Raffael Cavallaro, Ph.D.
    > <raffaelcavallaro...>
  • > FWIW, this sounds like a problem I have when using EyeTV.  When I
    > start the program when there is some network problem, EyeTV takes a
    > while before the beach ball stops spinning.

      Suffice to say there's a bug. It's best to file a report and move
    the discussion to the xcode-users list as this has nothing at all to
    do with Cocoa.

    --
    I.S.
  • I'm not sure how, but this thread seems to have migrated to cocoa-dev

    Please take it back to xcode-users

    thanks

    scott

    On Nov 1, 2007, at 11:23 AM, Raffael Cavallaro wrote:

    >
    > On Nov 1, 2007, at 10:55 AM, Chris Espinosa wrote:
    >
    >> and Xcode doesnt cuntinue until the DNS server times out.
    >
    > Wouldn't the obvious solution be to not have Xcode wait on a server
    > timeout?
    >
    >
previous month november 2007 next month
MTWTFSS
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    
Go to today