Hi Jayson,
On Sep 8, 2009, at 4:51 PM, Jayson Adams wrote:
On Sep 8, 2009, at 3:31 PM, Marc Krochmal wrote:
Hi Brent,
I may have been one of those appalled Apple engineers. In general,
[NSHost currentHost] is the worst API on the system and people
should avoid it like the plague.
Hi
On Sep 8, 2009, at 3:31 PM, Marc Krochmal wrote:
Hi Brent,
I may have been one of those appalled Apple engineers. In general,
[NSHost currentHost] is the worst API on the system and people
should avoid it like the plague.
Hi Marc,
Can you tell why this is so?
Best,
__jayson
Circus
Hi Brent,
I may have been one of those appalled Apple engineers. In general,
[NSHost currentHost] is the worst API on the system and people should
avoid it like the plague.
Jonathan, just use SCDynamicStoreCopyLocalHostName instead.
gethostname probably isn't going to do what you want.
While I don't speak for Apple, we ran into this with Daylite Server,
and found out that you shouldn't be using those calls.
I got a similar response, I had been using NSHost previously and
hadn't noticed any delay so assumed it was using a local backing
store. I ran the same code on the net
On 8 Sep 2009, at 22:44, Brent Gulanowski wrote:
While I don't speak for Apple, we ran into this with Daylite Server,
and found out that you shouldn't be using those calls.
Basically, your computer is NOT the authority on your computer's
host name. The DNS system is the authority. So these
On 8 Sep 2009, at 22:37, Jean-Daniel Dupas wrote:
Le 8 sept. 2009 à 22:15, jonat...@mugginsoft.com a écrit :
I am not sure if this is a problem unique to me or not but under
10.5 [[NSHost currentHost] name] or [[[NSProcessInfo] processInfo]
hostname] were quick and easy ways to get an mDN
While I don't speak for Apple, we ran into this with Daylite Server, and
found out that you shouldn't be using those calls.
Basically, your computer is NOT the authority on your computer's host name.
The DNS system is the authority. So these calls tend to trigger DNS lookups,
at which point you're
On 8 Sep 2009, at 22:24, Jens Alfke wrote:
On Sep 8, 2009, at 1:15 PM, jonat...@mugginsoft.com wrote:
I am not sure if this is a problem unique to me or not but under
10.5 [[NSHost currentHost] name] or [[[NSProcessInfo] processInfo]
hostname] were quick and easy ways to get an mDNS frien
Le 8 sept. 2009 à 22:15, jonat...@mugginsoft.com a écrit :
I am not sure if this is a problem unique to me or not but under
10.5 [[NSHost currentHost] name] or [[[NSProcessInfo] processInfo]
hostname] were quick and easy ways to get an mDNS friendly hostname
such as imac-2.local
On 10.6
I am not sure if this is a problem unique to me or not but under 10.5
[[NSHost currentHost] name] or [[[NSProcessInfo] processInfo]
hostname] were quick and easy ways to get an mDNS friendly hostname
such as imac-2.local
On 10.6 I find that both these combinations block badly (NSProcessInfo
10 matches
Mail list logo
