Re: [reSIProcate] Status of faststreams?
FYI - I fixed the reTurn issue "asio::ip:address cannot be inserted
into a faststream" last week.
Scott
On Mon, Nov 24, 2008 at 8:03 AM, Justin Matthews <jmatthewsr@xxxxxxxxx> wrote:
> The faststreams implementation has been thoroughly tested for the stack and
> DUM on Windows. It has not been widely tested with the other parts of
> resip. At this point I don't think it should be enabled by default. As
> more developers use it and it gets some additional testing in non-windows
> environments and additional testing in all areas of resip at some point it
> would be reasonable to enable by default. Enabling by default would require
> some developers to make changes to support faststreams, so it would not be
> an isolated change to the resip codebase.
>
> I will take a look at the build issues (although probably not until after
> the holiday). Thanks for the report.
>
> -justin
>
> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxx
> [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxx] On Behalf Of Max Bowsher
> Sent: Monday, November 24, 2008 6:12 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxx
> Subject: [reSIProcate] Status of faststreams?
>
> Hi,
>
> What is the status of the faststreams code in Resiprocate 1.4.1, and should
> it really be enabled by default?
>
> Whilst it does seem to work ok to build the stack, DUM, and repro, building
> other parts of resiprocate source tree fails with numerous compiler errors:
> - resip/stack/test/testStack.cxx
> rutil Inserter doesn't work with faststream
> - reTurn/**
> asio::ip:address cannot be inserted into a faststream
> - tfm/**
> Makes numerous direct references to STL streams
>
>
> Defining RESIP_USE_STL_STREAMS allows these things to build.
>
> Max.
>
>
>
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxx
> https://list.resiprocate.org/mailman/listinfo/resiprocate-devel
>