Hi Odi, >> 5. Implement test cases based on 4 and debug the code that we have. >> (Includes extending the JavaDocs based on 4.) > > > Some profiling would be good, too, to spot obvious performance loss.
Good point, though I'm not sure whether I'm going to invest the time in performance optimization as long as the functionality is lacking. Splitting the background thread in two to enable pipelining will be a small step. Implementing dispatchers that use more than one connection will be a major change. Anyway, profiling can be done on http-core as well as http-async. And with a quicker return on investment, I guess :-) > BTW: Check out Eclipse TPTP. It has a fantastic profiler that can even > be used remotely. I loathe all kind of integrated development environments, mostly because none of them uses Emacs as their editor. But I'll include Eclipse TPTP in the list of profilers to consider when the time comes. Thanks for the tip. cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
