So it is a single task loop. ? Either each callback call must do small amounts of work or if it must live for a long time a worker thread is created and the callback only passes info to the message queue for that thread ???? Old mongoose managed this for us by creating a thread but prevented us from writing task like code where each piece of data is worked on each call a little at a time???
On Thu, Aug 7, 2014 at 11:52 AM, Sergey Lyubka <[email protected]> wrote: > On Thu, Aug 7, 2014 at 4:51 PM, Scott Ellis <[email protected]> > wrote: > >> Ok but if a user callback takes a while to complete, it appears that >> mongoose will not serve the next request until the previous user callback >> completes. Is that correct? > > > That is correct. > > -- > You received this message because you are subscribed to the Google Groups > "mongoose-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/mongoose-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "mongoose-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/mongoose-users. For more options, visit https://groups.google.com/d/optout.
