Hi, I'd leave ns_http in the core for now -- should be no problem with updates like this.
For this functionality, I think you may be able to get the same effect with tclcurl and a bunch of callbacks among other features. But, ns_http waitall does seems cleaner. -Jim On Dec 13, 2011, at 5:03 PM, Jeff Rogers wrote: > Hey all, > > I'm in the process of making some additions to ns_http (especially a > "waitall" subcommand that waits for any outstanding request to finish; > useful when you're making a lot of requests) and I got to wondering if > ns_http would be better as an external module (where it might be more > flexible to update) or if people prefer it in the core. > > Thoughts? > > -J > > > ------------------------------------------------------------------------------ > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > This paper surveys cloud computing today: What are the benefits? > Why are businesses embracing it? What are its payoffs and pitfalls? > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > _______________________________________________ > aolserver-talk mailing list > aolserver-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/aolserver-talk ------------------------------------------------------------------------------ Cloud Computing - Latest Buzzword or a Glimpse of the Future? This paper surveys cloud computing today: What are the benefits? Why are businesses embracing it? What are its payoffs and pitfalls? http://www.accelacomm.com/jaw/sdnl/114/51425149/ _______________________________________________ aolserver-talk mailing list aolserver-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/aolserver-talk
