There is already a thread going about issues with the VisitorFilter. This is just my rant about the design. Hopefully it will not be taken as bashing and instead as input for a better design.

When designing a scalable application you want to avoid unnecessary hits to the database. The Visitor hits at least once for inserting or updating. I think it may also try to create each time.

Why is the visitor information not just stored in the cookies? It seems like the VisitorFilter is duplicating the function of cookies.

This is only from a cursory view of the code and checking on some complaints from the IRC chat.

-- David

Reply via email to