Ah, so you're not using it to cache the views. No one seems to. Odd. I've migrated my worst views into this pattern with little trouble. The improvements seem great. There were a handful of page elements that were customized based on the request status. In order to handle those, I've been replacing them with placeholders that I regex out.
FWIW, I wasn't happy with the SqlAlchemy caching after a while. I opted for a custom dogpile based caching scheme instead. For permissions/groups, I just store a list of ids. For "objects", I convert the columns to dicts and store those, I deserialize into a Pylons style "AttibuteSafe" Dictionary. If I need to handle a relationship, I add in some lambda functions when deserializing. This ended up being a lot faster and with a much smaller memory imprint than caching the SqlAlchemy objects. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
