Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <034d01c148c6$b4b108b0$01000001@lifelesswks>
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin AT cygwin DOT com>
References: <3BB4604A DOT 13127 DOT 3BDEA3F AT localhost>
Subject: Re: qmail-1.03: any volunteers?!
Date: Sat, 29 Sep 2001 19:11:20 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 29 Sep 2001 09:18:42.0901 (UTC) FILETIME=[BBC4C050:01C148C7]

----- Original Message -----
From: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
To: <cygwin AT cygwin DOT com>
Sent: Friday, September 28, 2001 7:34 PM
Subject: Re: qmail-1.03: any volunteers?!


> > Stipe Tolj schrieb am 2001-09-28 11:00:
>
> >> What about daemontools, ucspi-tcp, djbdns, are they not needed?
> >
> >For the fast shot I used inetd to invoke qmail-smtpd and qmail-pop3d,
> >which did work.
> >
> >BTW, I used bind-8.1.2-1 binaries I found at the Cygwin RPM project
at
> >SourceForge.
>
> Hmpf, I don't like bind.  I think we should have a 'cygwin'-solution
> for dns lookups.  There is a complete resolver in squid included,
> (I read it somewhere in the mail archives), maybe it is possible to
> reuse it as standalone resolver?  Or is it possible to build djbdns?
> What is adns?  I built adns, but is it a resolver or does it depend
> on bind, too?

Win32 has a built in resolver, which cygwin exposes via gethostby*. If
you need async resolving capabilities, you can a) use pthreads or b)
roll your own from somewhere else. The squid resolver is in three parts,
1) A library containing a implementation of the RFC to allow querying of
DNS servers.
2) Client code to make requests to the library, and handle in-squid
housekeeping.
3) An IP address->name cache for efficiency.

It can be reused quite happily. It's designed to be used with
non-blocking I/O and a select or poll engine in the calling software.
However the RFC implementation has 0 caching of results - thats handled
in squid, using squid's hash table primitives. So that would need to be
added to any 'solution'.

Rob



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/