Richard, For us, revServer is a black box that we don't have the time or inclination to deal with, at this point. Others, of course, may not be in the same situation we are in.
I do think revServer has the most potential of all the products Runrev sells. It just needs some docs, and, perhaps fixes. JD On Aug 2, 2010, at 10:02 AM, Richard Gaskin wrote: > Jerry wrote: > > > Based on Andrew's research (I believe it was a report he voluntarily > > did for Runrev) and our observations, the timeout is not 30 seconds > > for one process. We think there is some sort of pooling of processes > > (and possibly users) that are limited by 30 secs. We have seen the > > timeout in much shorter time spans. Andrew reports a 4 second time > > out. > > Thanks for the clarification. > > Since RevServer spawns a separate process for each request, how and why does > it bother limiting aggregate usage? > > I suspect this is a bug and will be addressed in the next build. > > -- > Richard Gaskin > Fourth World > Rev training and consulting: http://www.fourthworld.com > Webzine for Rev developers: http://www.revjournal.com > revJournal blog: http://revjournal.com/blog.irv > _______________________________________________ > use-revolution mailing list > use-revolution@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
