< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Changes required to compile reSIProcate under Cygwin


Hi,

Thank you Adam, I'm glad to see that integrating new changes (from the
community) into reSIProcate seems painless (as long as the changes
make sense :) ).

I haven't been much active on the reSIP* mailing lists, but I've been
using/looking at the stack and the dum for quite some time now. Having
looked at various SIP stacks I am not afraid to say that reSIProcate
has been - and is currently - at the top of my list.

I especially like the OO approach of the dum and the fact that the
stack is threading model agnostic.

I hope to contribute even more and am looking forward to it.

Regards,
Francis

On Wed, Nov 19, 2008 at 3:32 PM, Adam Roach <adam@xxxxxxxxxxx> wrote:
> Thanks. I've tested the patch under OS X, and verified that it appears to
> cause no problems, so I've committed it (with only one minor change, related
> to the V6 comment below). I'm in the process of testing it under Linux,
> cygwin, and in Visual Studio Express 2005.
>
>
> On 11/19/08 12:48 PM, Francis Joanis wrote:
>>
>> - Cygwin doesn't seem to have any support for IPV6, so
>> Tuple::writeBinaryToken had to be changed
>>
>> I do not think the changes to the Tuple class are completely valid
>
> No, these are fine. In a non-V6 system, there is no way the system will
> create or attempt to use a V6 tuple, so this code wouldn't ever get
> exercised anyway.
>
> /a
>