| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
You would definitely need to pull nrappkit from Mozilla's codebase. We've had "fixing nICEr's public build" on the todo list for a while, but you're the first that has expressed an interest that I'm aware of. If you run into more breakage after pulling the current nrappkit (and you probably will, since the build system hasn't been fully updated yet) give me a shout and I can help.
Best regards,
Byron Campen
> _______________________________________________
> On Sep 19, 2015, at 7:05 AM, Volkan Hatem <volkan@xxxxxxxxx> wrote:
>
> Hi All,
>
> I am not sure if this is the right list to post about nICEr.
>
> Short:
>
> I'm trying to compile nICEr but it seems like changes copied from the gecko-dev repository without updates to nrappkit have broken it. Is there an up-to-date nrappkit repository I can use along with resiprocate/nICEr?
>
> Longer:
>
> I have been looking for an ICE implementation which supports TCP (especially TCP simultaneously-open) candidates. It seems like only firefox and chrome implement RFC 6544 on client side. Among the two, only nICEr seemed isolated enough to be used as an ICE library. Are there any alternatives in case back-porting changes from gecko to nICEr and nrappkit prove to require too much work?
>
> Best,
> -volkan
>
>
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel