You didn't understand ... my workers are used to offload the load of parsing the browser request payload from a string to a json object.
Anyway, I understand were you are taking SHTTPD. Currently SHTTPD's advantage over other libs is that it is not a black box, but provides an API to be used the way I want. I suggest doing both, keep the API and add the config-style. ________________________________________ From: Sergey Lyubka [mailto:[EMAIL PROTECTED] Sent: quarta-feira, 28 de Maio de 2008 12:17 To: Rui Jorge Coelho Cc: shttpd-general Subject: Re: [shttpd-general] Accept callback: threads and pipes On Wed, May 28, 2008 at 12:11 PM, Rui Jorge Coelho <[EMAIL PROTECTED]> wrote: Currently my worker threads actually just parse user request and send it via a pipe to another thread to avoid synchronization. Can I continue to do this using CVS ? I don't see why user must pasre anything at all. SHTTPD should be a black box: you just set the options, and have your callbacks called without any knowledge which thread is executing it. Also, shttpd_ctx is still per-thread, but I don't see we you set options (shttpd_register_uri and doc_root for example) for each worker thread. This is to be fixed, thanks for noting ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ shttpd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shttpd-general
