On Apr 24, 10:22 am, Jo <[email protected]> wrote: ... > 1) Five SQL statements are called per url (img, static html, css, js), > that's a lot of DB calls.
This is why I wrote my own system that performs only 1 DB call per session request. > 2) Sessions are attached to an app so there is no way to not use > sessions for some chosen urls. Most sites only need sessions after the > user has logged in. Some systems use session tracking on all users, logged in or not, but you're right, the lack of a choice means that there is that 5 call overhead for URLs when you're not even bothering with sessions yet. > Should we all use beaker or am I missing something and this is the way > it should be? No, it shouldn't be that each URL request translates to five hits on the database. With caching, in fact, I would say it sometimes shouldn't even cost one. But like I said before, writing your own system for this tends to take away a lot of these sorts of problems, at the expense of your own time, of course. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web.py" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/webpy?hl=en -~----------~----~----~----~------~----~------~--~---
