I agree there should be no such limit in any server-side engine, and
would be willing to bet this was put into RevServer to protect the
servers at on-rev.com and not intended for inclusion in the public
release for use on other hosts.
That said, 30 seconds is a LONG time on a server. In Internet time,
it's close to "forever". Add normal network latency and browser
rendering time to that and you've got some serious user expectation issues.
What server-side process could need that much time, and how many users
will wait for it?
--
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
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
