RE: [reSIProcate] Windows Name Resolution in reSIP
Thanks Cullen. I'll look at adding a compile flag as you suggested - but
since it's only synchronous it will not be a good solution for anything
other than a simple Soft phone UA.
Does anyone know if .NET has async DNS? I've looked around, but I can't
seem to find any reference to it. There is an asynchronous version of the
GetHostByName API - but the MSDN article says that the application should
not expect that the name will be resolved in parallel with other requests -
so I don't think this is ideal - also this function has been deprecated
since it does not support IP V6.
-----Original Message-----
From: Cullen Jennings [mailto:fluffy@xxxxxxxxx]
Sent: Tuesday, November 02, 2004 7:49 PM
To: Scott Godin; ReSiprocate
Subject: Re: [reSIProcate] Windows Name Resolution in reSIP
I seem to recall that the .NET stuff has async DNS but only supports A
record lookups
A compile time flag to just skip AREA and use the build in OS stuff seem
like a good thing to have whatever happens.
n 10/15/04 11:14 PM, "Scott Godin" <slgodin@xxxxxxxxxxxx> wrote:
> I've been looking into a way to get reSIP to use windows name resolution
along
> side with ares. This would allow reSIP to resolve names using Netbios,
WINS
> and hosts file on windows systems. The problem is that these functions
are
> synchronous and can block the stack.
>
> For now I've committed a solution that is synchronous - it works as
follows:
> - to enable on a WIN32 system - add compile flag:
> WIN32_SYNCRONOUS_RESOLUTION_ON_ARES_FAILURE
> - if ares DNS lookup fails then we fallback to Windows name
resolution
>
> Another draw back of this is that if a name really doesn't exist then it
will
> take twice as long to detect it. Ie. Ares needs to timeout then Win API
needs
> to timeout.
>
> If anyone has any bright idea's on a slick way to make these windows name
> resolution API's synchronous, then please share it. Until I can find a
good
> solution it will remain a compile flag.
>
> Thanks,
>
> Scott
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel