Thank you for the lighttpd howto. It looks very helpful. Hopefully, I will be able to clear some time next week to give it a go.
I noticed that, at the end, you spend time on URL remapping. "To benefit from this either routes.out of routes.py needs to be used or internal techniques need to be used to selectively eliminate '/app/ default' from URLs." Do I care about this? In fact, I do not care what a URL looks like - no-one is going to be typing these URLs into a browser. Can you simplify your recipe by removing this, and focusing on the low memory usage, which I do care about. Or at least separating out the URL mapping into a seperate section - the rest of the recipe is so well organized and readable. On Feb 13, 2:42 am, John Heenan <johnmhee...@gmail.com> wrote: > As requested I have placed a howto on web2pysplices > athttp://www.web2pyslices.com/main/slices/take_slice/57 > > I have written a considerable preface to clarify issues and to > indicate why we should pay attention to issues concerned with keeping > memory use low. > > John Heenan > > On Feb 13, 2:41 am, mdipierro <mdipie...@cs.depaul.edu> wrote: > > > I think this is an excellent point. > > > > My data demonstrated a 40MB memory solution is feasible. > > > > I am absolutely amazed and disappointed I cannot get such simple > > > points gracefully acknowledged by a self styled 'expert' and by the > > > moderator. > > > The reason I suggested opening a new thread was to eliminate the > > digression. > > Would you write a short howto on web2pyslices on how to achieve this > > small memory footprint? > > Eventually it could become a section in the book. > > > Massimo -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
