• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Carbon CFM callbacks for CFNetServices
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Carbon CFM callbacks for CFNetServices


  • Subject: Re: Carbon CFM callbacks for CFNetServices
  • From: "Dean Dauger" <email@hidden>
  • Date: Tue, 21 May 2002 13:59:54 -0700

> At 7:10 -0700 21/5/02, Dean Dauger wrote:
>> That is,
>>can I depend on this mechanism working in current and future versions of OS
>>X?
>
> Apple's official policy (as set by *way* upper management--please
> don't shoot the messenger) is that developers should move away from
> CFM and towards Mach-O, which obviates the need for a supported
> version of NewRoutineDescriptor (which is basically what this code
> does). Hence we have no plans to introduce such a call. Therefore,
> if you continue to use CFM you must use ugly hacks like this. Sorry.
>
> Having said that, I must admit that I do most of my X development in
> Mach-O these days. CodeWarrior Mach-O rocks! Of course, that's not
> much help if you want to continue to deploy on Mac OS 9 (unless you
> go the packaged route, which is kinda klunky, especially for pre 9.0
> users).
>
> *sigh*
>
> S+E
> --
> Quinn "The Eskimo!" <http://www.apple.com/developer/>
> Apple Developer Technical Support * Networking, Communications, Hardware

Hi,

Thanks a lot for your reply! Yes, that policy is not that surprising, and I
got that feeling at WWDC, but it's nice to hear from someone like you to
help connect the dots. Thank you.

As for my being able to move to Mach-O, it's "not yet". Many of my users
use OS 9 or mixed computing clusters of Macs running OS 9 and OS X, so I
clearly need my code to support both (I've been using NSL/SLP for a year and
a half now). My estimate is that my users will probably need 9
compatibility for a couple years still.

However, I see Rendezvous as a good thing, and, with the help of Kevin
Arnold and Marc Krochmal of Apple, I have a migration path into
Rendezvous/ZeroConfig. To do the migration, though, I'm hoping that the CFM
callback hack will last until the migration is complete, and then I can
switch everything over to Mach-O.

Thanks for the tips! The people on this list have been very helpful.

Thanks,
Dean
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Carbon CFM callbacks for CFNetServices
      • From: Chris Silverberg <email@hidden>
  • Prev by Date: Re: Getting data rate for a newtork interface
  • Next by Date: Getting the IP addressing method
  • Previous by thread: Re(2): Carbon CFM callbacks for CFNetServices
  • Next by thread: Re: Carbon CFM callbacks for CFNetServices
  • Index(es):
    • Date
    • Thread