• 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: Name resolution limits
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Name resolution limits


  • Subject: Re: Name resolution limits
  • From: Josh Graessley <email@hidden>
  • Date: Thu, 07 Feb 2002 17:35:23 -0800

I believe I'm mistaken. There are a few APIs that are thread safe. I think
gethostinfo and getaddrinfo may be thread safe. This means you could do
multiple lookups if you have multiple threads. It does seem like overkill to
spawn 10 threads if you need to perform 10 lookups simultaneously, but with
the public APIs, that's the only way to do it.

-josh

On 2/7/02 5:20 PM, "Josh Graessley" <email@hidden> wrote:

> Using any name resolver APIs on X, you can only get 1 lookup at a time per
> process.
>
> There are a few problems:
> 1) The resolver APIs are blocking, so you can have no more than one lookup
> per thread at any given time.
> 2) The resolver APIs are not thread safe, so you can only have one thread
> performing a lookup.
>
> This gives you a limit of one lookup per process. Since the OpenTransport
> APIs just map to the built-in resolver APIs, it has the same limitation.
>
> On Mac OS 9, I believe there was no hard limit on the number of simultaneous
> lookups. Available memory was the only limitation.
>
> -josh
>
> On 2/7/02 5:08 PM, "jud spencer" <email@hidden> wrote:
>
>> There was some discussion here a while back about the limits to the number
>> of name lookups that can take place at one time using OT.
>>
>> Can I hear what the exact limits are? Is it one lookup at a time? What are
>> the limits running under OS9 using Carbon? Is it the same as an OS9
>> InterfaceLib version?
>>
>> The OSX version of LetterRip is getting some horrible performance in the MX
>> lookup area. We currently don't cache MX lookup info, should I consider
>> doing that now or is the current limitation short-term?
>>
>> jud
>> _______________________________________________
>> 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.
> _______________________________________________
> 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.
_______________________________________________
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: Name resolution limits
      • From: Stéphane Sudre <email@hidden>
References: 
 >Re: Name resolution limits (From: Josh Graessley <email@hidden>)

  • Prev by Date: Re: Name resolution limits
  • Next by Date: Re: Name resolution limits
  • Previous by thread: Re(2): Name resolution limits
  • Next by thread: Re: Name resolution limits
  • Index(es):
    • Date
    • Thread