#803: ExtendingVisitFramework
--------------------------------+-------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: anonymous
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: CherryPy | Version: 0.9a5
Severity: normal | Keywords:
--------------------------------+-------------------------------------------
I just went though the visit framework after reading this:
http://trac.turbogears.org/turbogears/wiki/ExtendingVisitFramework
Considering that the identity schema was recently moved out of the TG
internals, what would people feel about moving visit?
I have one project where visit as-is is perfect
I have another where I'd like to add 'ip , hitcount, start, end'
the current plugin framework makes that possible by using the current
visit table and then a second + a plugin.
i'd kind of like to consolidate it into one by doing this:
* move TG_Visit to model.py, where fields can be added
* create hook functions in the visit manager that will call a user
defined function at the appropriate time
ie:
{{{
class SqlAlchemyVisitManager():
def new_visit()
visit = model.TG_Visit()
visit.commit()
}}}
model.py
{{{
class TG_Visit():
# current TGVisit columns required
# chance to overwrite udpate_visit
}}}
--
Ticket URL: <http://trac.turbogears.org/turbogears/ticket/803>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Tickets" 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/turbogears-tickets
-~----------~----~----~----~------~----~------~--~---
