Session Tracking
I’m currently playing around a lot with web caching and performance related work (my Masters Thesis in the area is due shortly), so I’m finding quite a few interesting articles on the subject.
Currently thinking through which parts of my OASIS-Akl application needs to be session tracked, and which parts don’t. It’s not just a case of session tracking for funky dynamic stuff, there are security issues too. So while some of the images don’t need to be tracked, I do need to make sure that they’re not served to users who aren’t logged in, for example.
I’m playing with using the Varnish http proxy to assemble pages from multiple page fragments (using esi:include). The neat bit is using Varnish’s VCL language to strip session (cookie) information from the page fragments that don’t need it, thus allowing them to be cached. So for example for a typical page with a fairly dynamic menu on the left that isn’t user specific, that menu can be cached, while the main page content is user specific and keeps session information (or could perhaps be cached per-user)
Interesting topic and I’m getting quite into it. Lots to learn though.
Wasted quite a few hours with failing to get ESI to work, but it looks like the problem was some sort of conflict between varnish and the cherrypy.wsgi web server I’m using - chunked encoding is killing varnish. Not sure where the fault is, but I can avoid tripping it by returning pages from cherrypy in one go rather than piecemeal.
Interesting Links
компютри втора употребаput-the-web-server-on-a-diet-and-increase-scalability??????
- Colin