serf currently calls abort() in certain situations, for example when
parsing data returned from the header, and that data isn't correct.
Since serf is a library, it should *never*, *ever* call abort(). Instead,
it should return an error.
An abort() call will tear down the whole application.
Just in case you think calling abort() is acceptable: imagine a webbrowser
would simply exit just because some buggy website returns unexpected data.
I don't think anyone would like that but wants to see an error instead.
Original issue reported on code.google.com by tortoisesvn on 5 May 2007 at 6:30
Original issue reported on code.google.com by
tortoisesvn
on 5 May 2007 at 6:30