RE: [reSIProcate] Stability for use in commercial release
Thanks, Alan. I moved forward to the latest stuff in subversion. It
cleared up the memory corruption and the assert in the logger, which was
nice. First thing I tried still cored, though. I filed an issue through
sipfoundry -- hope that was the right thing to do.
--C
> -----Original Message-----
> From: Alan Hawrylyshen [mailto:alan@xxxxxxxxxx]
> Sent: Tuesday, June 08, 2004 11:24 AM
> To: Craig Kaes
> Cc: 'resiprocate-devel@xxxxxxxxxxxxxxxxxxx'
> Subject: Re: [reSIProcate] Stability for use in commercial release
>
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> On Jun 8, 2004, at 10:37, Craig Kaes wrote:
>
> >
> > I do, however, have some concerns about the stability of
> resiprocate.
> > I've
> > seen postings of memory leaks and list a couple of my own problems
> > below. I
> > have three questions --
> > 1) Are folks using this stack for commercial offerings?
>
> Yes -- there are at least two companies using reSIProcate within more
> than 4 commercial projects.
>
> > 2) For those who are, are you happy with it?
>
> We are very happy with reSIProcate vs. many other libraries we
> evaluated or were using previously.
>
> > 3) I've done my testing on the plain ol' tarball
> release (0.4.0).
> > Should I be trying out head? Is there a more recent label
> with fewer
> > issues?
>
>
> I would strongly suggest using the latest code from SVN. If
> you need a
> tarball, I'd be
> happy to prepare a pre-0.5 tarball for you. There have been
> some fixes
> to some memory problems since 0.4.
>
> These issues are certainly a high-priority concern for all of us
> relying on the stack commercially.
>
> I am tweaking some of the things affected by the migration to
> subversion and SipFoundry, once these are complete there will
> be a 0.5
> tarball available.
>
> Cheers,
>
> Alan Hawrylyshen
> Jasomi Networks Inc.
> a l a n a t j a s o m i d o t c o m
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.2 (Darwin)
>
> iD8DBQFAxfYj2t1B785xGCgRAgOnAJ40J0Lgj0P+6jEUnjFPwK0T6WswEACfScrP
> WIhImb1eqZyAl1vNjZquPXc=
> =o40y
> -----END PGP SIGNATURE-----
>