Matthew Scott wrote:
Jeff + anyone else playing with identity/visit, etc...
Just wanted to draw attention to this patch that makes TurboGears
honor "visit.on = False" in config files:
http://trac.turbogears.org/turbogears/ticket/373
As I mention in the ticket, this patch prevents Visit Tracking from
being enabled in paths below the root. The nature of CherryPy's config
system is such that the config option is checked repeatedly for each
path component.
This patch would disable Visit Tracking for the entire site regardless
of whether it was enabled for subpaths.
Also wanted to ask about the possibility of having alternate providers
for VisitorFilter. For instance, I've written an alternate provider
for identity that I use like this in dev.cfg:
identity.provider = "schevo.gears.identity.SchevoIdentityProvider"
The IdentityProvider protocol has changed a bit. You'll want to take a
look at the default SqlObjectIdentityProvider
(turbogears.identity.soprovider) to get a sense of what's changed. I
hope to document this *soon*.
You can also plug in a visitor by adding an entry point for
turbogears.visit (I think). This plug in should have two methods
(new_visit and record_request) and will be called by the Visit Tracking
system when appropriate. Identity is now implemented as just another
plug in to Visit Tracking.
There are people (myself included) that are stubborn enough to not use
a SQL database with TurboGears, but still reap whatever rewards
possible. :)
Weirdos.
So what I'd ideally like to do is:
visit.provider = "schevo.gears.visit.SchevoVisitProvider"
If your egg exports a Visit plug in, it will be loaded at start up. This
works much like template plug ins. The only difference is it seems
reasonable to be able to limit or order the visit plug ins. (Someone
want to file a Ticket?)
