I'm not suggesting that. I'm suggesting that packages adopt a standard
hook to detect bots and invoke an alternate session.
Otherwise, a custom SessionFactory is needed and the convenience methods
that create the various session factories from the environment configs are
unusable. Thats fine for advanced users, but a bit out-of-reach for newer
users.
Imagine there's a package like `pyramid_session_bots` to handle detection.
It has two methods:
def is_bot_request(request):
"examines request"
return True or False
def new_bot_cookie_session(request):
return CookieSessionFactory()
That's easy to use on a custom SessionFactory
A junior user would just want to use the config based session factory.
The easiest way to support this in various session projects, would be to
standardize how they could leverage this package (or a better competitor).
The harder way would be for that package to create/manage a custom session
factory. That's because they all implement the
`session_factory_from_settings` differently. For example, pyramid_beaker
is straightforward, but pyramid_redis_sessions has a bit of logic in its
includeme.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
