Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migration from shttp_d puzzling #16

Closed
GoogleCodeExporter opened this issue Nov 13, 2015 · 2 comments
Closed

Migration from shttp_d puzzling #16

GoogleCodeExporter opened this issue Nov 13, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

I have been using SHTTPD as an API in a Windows Visual C++ Project. I would
like to migrate to mongoose.Is this always possible? Are notes available
for guiding would-be migrants such as myself?

With SHTTPD callbacks are called repeatedly until the request and response
are finished. This was controlled by shttpd_arg.flags. It is not clear to
me how this is handled by mongoose. Is the callback called only once? Must
MAX_REQUEST_SIZE be large enough to hold the largest possible transmission? 

Thanks.


Original issue reported on code.google.com by frank.me...@gmail.com on 12 Feb 2009 at 8:09

@GoogleCodeExporter
Copy link
Author

In Mongoose, each connection is handled by its own thread. So, the callback may
output as many data as it wants, and even block. Callback is called only once 
per
request.

Original comment by valenok on 12 Feb 2009 at 9:17

@GoogleCodeExporter
Copy link
Author

Please see http://code.google.com/p/mongoose/wiki/ArchitectureNotes

Original comment by valenok on 11 Mar 2009 at 9:41

  • Changed state: WontFix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant